How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cancer.gov Staging API

Staging Algorithms

Cancer.gov Staging API is one of 48 APIs that Cancer.gov publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Staging. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, rate-limit docs, and an API reference.

This API exposes 35 operations across 25 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.seer.cancer.gov.

35 operations 25 paths 23 schemas 4 DELETE16 GET11 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://clinicaltrialsapi.cancer.gov/api/v2
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Cancer.gov Staging API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-SEERAPI-Key (apiKeyScheme). By default, every request must be authenticated.

Paths & Operations 35

Across 25 paths, the API surfaces 35 operations — 4 DELETE, 16 GET, 11 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Staging 35

Staging Algorithms

GET
/rest/staging/{algorithm}/{version}
Return information about a specific algorithm version
getVersion 2 params → 200404
PUT
/rest/staging/{algorithm}/{version}
Update an algorithm version
updateVersion 2 params body → 200400404
POST
/rest/staging/{algorithm}/{version}
Create a new version for an algorithm
createVersion 2 params body → 201400404
DELETE
/rest/staging/{algorithm}/{version}
Delete an algorithm version
deleteVersion 2 params → 204404
GET
/rest/staging/{algorithm}/{version}/table/{id}
Return a single table
getTable 3 params → 200404
PUT
/rest/staging/{algorithm}/{version}/table/{id}
Update a table
updateTable 4 params body → 200400404
DELETE
/rest/staging/{algorithm}/{version}/table/{id}
Delete a table
deleteTable 4 params → 204400404
GET
/rest/staging/{algorithm}/{version}/schema/{id}
Return a single schema
getSchema 3 params → 200404
PUT
/rest/staging/{algorithm}/{version}/schema/{id}
Update a schema
updateSchema 4 params body → 200400404
DELETE
/rest/staging/{algorithm}/{version}/schema/{id}
Delete a schema
deleteSchema 4 params → 204400404
GET
/rest/staging/{algorithm}
Return information about a specific algorithm
getAlgorithm 1 param → 200404
PUT
/rest/staging/{algorithm}
Update an algorithm
updateAlgorithm 1 param body → 200400404
POST
/rest/staging/{algorithm}
Create a new algorithm
createAlgorithm 1 param body → 201400
DELETE
/rest/staging/{algorithm}
Delete an algorithm
deleteAlgorithm 1 param → 204400404
POST
/rest/staging/{algorithm}/{version}/{id}/defaults
Get all schema defaults
getSchemaInputDefaults 3 params body → 200400404
POST
/rest/staging/{algorithm}/{version}/table
Create a new table
createTable 3 params body → 201400
POST
/rest/staging/{algorithm}/{version}/table/{id}/match
Checks whether a set of key/value pairs match any row in a table
matchTable 3 params body → 200404
POST
/rest/staging/{algorithm}/{version}/stage
Stage a case
stageSchema 2 params body → 200400
POST
/rest/staging/{algorithm}/{version}/schemas/lookup
Perform a schema lookup
listSchemas 2 params body → 200404
POST
/rest/staging/{algorithm}/{version}/schema
Create a new schema
createSchema 3 params body → 201400
POST
/rest/staging/{algorithm}/{version}/invalidate_cache
Invalidate algorithm version cache
invalidateCache 2 params → 204404
POST
/rest/staging/{algorithm}/{version}/fill_cache
Fill algorithm version cache
fillCache 2 params → 204404
POST
/rest/staging/{algorithm}/{version}/copy
Copies all schemas and tables to another algorithm/version
copyVersion 2 params body → 204400404
GET
/rest/staging/{algorithm}/{version}/tables
Return a list of matching tables
listTables 4 params → 200404
GET
/rest/staging/{algorithm}/{version}/tables/history
Return a list of table history entries
listTablesHistory 5 params → 200400404
GET
/rest/staging/{algorithm}/{version}/table/{id}/schemas
Return a list of the schemas which use a specific table
getInvolvedSchema 3 params → 200404
GET
/rest/staging/{algorithm}/{version}/table/{id}/history
Return the history of single schema
getTableHistory 6 params → 200400404
GET
/rest/staging/{algorithm}/{version}/table/{id}/glossary
Return a matching glossary keywords from the table
getTableGlossary 5 params → 200404
GET
/rest/staging/{algorithm}/{version}/schemas
Return a list of schemas
listSchemas_1 3 params → 200404
GET
/rest/staging/{algorithm}/{version}/schemas/history
Return a list of schema history entries
listSchemasHistory 5 params → 200400404
GET
/rest/staging/{algorithm}/{version}/schema/{id}/tables
Return a list of the tables involved in a specific schema
getInvolvedTables 3 params → 200404
GET
/rest/staging/{algorithm}/{version}/schema/{id}/history
Return the history of single schema
getSchemaHistory 6 params → 200400404
GET
/rest/staging/{algorithm}/{version}/schema/{id}/glossary
Return a matching glossary keywords from the schema
getSchemaGlossary 5 params → 200404
GET
/rest/staging/{algorithm}/versions
Return information about all the supported versions of an algorithm
getVersions 1 param → 200404
GET
/rest/staging/algorithms
Return a list of all staging algorithms
getAlgorithms → 200

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are StagingSchema (18 properties), StagingTable (16 properties), StagingSchemaInput (12 properties), Input (12 properties). Each schema is shown below with its type and property counts.

SchemaProjection
object
4 properties
StagingSchemaInput
object
12 properties
StagingTable
object
Table
16 properties
StagingAlgorithmVersion
object
Target algorithm/version
6 properties
StagingSchemaInfo
object
7 properties
TableProjection
object
3 properties
Input
object
12 properties
StagingTablePath
object
5 properties
ApiKeywordMatch
object
6 properties
StagingMetadata
object
3 properties
Metadata
object
3 properties
TableMatch
object
2 properties
StagingSchemaHistory
object
9 properties
StagingAlgorithm
object
Algorithm information
3 properties
StagingKeyValue
object
2 properties
StagingData
object
6 properties
StagingTableHistory
object
9 properties
StagingSchema
object
Schema
18 properties
StagingKeyMapping
object
2 properties
StagingColumnDefinition
object
4 properties
StagingSchemaOutput
object
8 properties
StagingMapping
object
6 properties
Error
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cancer-gov-staging-api-openapi.yml Raw ↑

Other APIs Cancer.gov publishes across the network.

NCI Clinical Trials Search API
NCI Genomic Data Commons (GDC) API
NCI Content Syndication Services
Cancer.gov Diseases API
Cancer.gov Interventions API
Cancer.gov Terms API
Cancer.gov Trials API
Cancer.gov Application version endpoint API
Cancer.gov Asset Details Controller API
Cancer.gov Autosuggest API
Cancer.gov Concept endpoints API
Cancer.gov Delete Collection Controller API
Where this information came from

This is an independent, third-party profile of Cancer.gov Staging API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.