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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cancer.gov

Cancer.gov Concept endpoints API

The Concept endpoints API from Cancer.gov — 21 operation(s) for concept endpoints.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cancer.gov Concept endpoints 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 Concept endpoints. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, rate-limit docs, and an API reference.

This API exposes 21 operations across 21 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 2.4.1.RELEASE.

Requests are made against a single base URL, /.

21 operations 21 paths 19 schemas 21 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.4.1.RELEASE
Base URL
https://clinicaltrialsapi.cancer.gov/api/v2
Contact
NCI EVS
Terms of Service
View terms
Resource Areas
1

Paths & Operations 21

Across 21 paths, the API surfaces 21 operations — 21 GET. Each is listed below with its method, path, parameters, and response codes.

Concept endpoints 21
GET
/api/v1/concept/{terminology}
Get concepts specified by list parameter
getConcepts 4 params → 400417404200
GET
/api/v1/concept/{terminology}/{code}
Get the concept for the specified terminology and code
getConcept 5 params → 400417404200
GET
/api/v1/concept/{terminology}/{code}/subtree
Get the entire subtree from the root node to the specified code
getSubtree 4 params → 400404200
GET
/api/v1/concept/{terminology}/{code}/subtree/children
Get the entire subtree from the root node to the specified code
getSubtreeChildren 4 params → 400404200
GET
/api/v1/concept/{terminology}/{code}/roles
Get roles for the specified terminology and code
getRoles_1 3 params → 404200
GET
/api/v1/concept/{terminology}/{code}/pathsToRoot
Get paths to the hierarchy root from the specified code
getPathsToRoot 6 params → 417404200
GET
/api/v1/concept/{terminology}/{code}/pathsToAncestor/{ancestorCode}
Get paths from the specified code to the specified ancestor code
getPathsToAncestor 7 params → 417404200
GET
/api/v1/concept/{terminology}/{code}/pathsFromRoot
Get paths from the hierarchy root to the specified concept
getPathsFromRoot 6 params → 417404200
GET
/api/v1/concept/{terminology}/{code}/parents
Get parent concepts for the specified terminology and code
getParents 3 params → 404200
GET
/api/v1/concept/{terminology}/{code}/maps
Get maps for the specified terminology and code
getMaps 3 params → 404200
GET
/api/v1/concept/{terminology}/{code}/inverseRoles
Get inverse roles for the specified terminology and code
getInverseRoles 3 params → 404200
GET
/api/v1/concept/{terminology}/{code}/inverseAssociations
Get inverse associations for the specified terminology and code
getInverseAssociations 3 params → 404200
GET
/api/v1/concept/{terminology}/{code}/history
Get history for the specified terminology and code
getHistory 3 params → 404200
GET
/api/v1/concept/{terminology}/{code}/disjointWith
Get "disjoint with" info for the specified terminology and code
getDisjointWith 3 params → 404200
GET
/api/v1/concept/{terminology}/{code}/descendants
Get descendant concepts for the specified terminology and code
getDescendants 6 params → 417404200
GET
/api/v1/concept/{terminology}/{code}/children
Get child concepts for the specified terminology and code
getChildren 3 params → 404200
GET
/api/v1/concept/{terminology}/{code}/associations
Get the associations for the specified terminology and code
getAssociations_1 3 params → 404200
GET
/api/v1/concept/{terminology}/subsetMembers/{code}
Get subset members for the specified terminology and code
getSubsetMembers_1 6 params → 417404200
GET
/api/v1/concept/{terminology}/roots
Get root concepts for the specified terminology
getRoots 3 params → 417404200
GET
/api/v1/concept/{terminology}/codes
Get all codes for the specified terminology
getAllCodesForTerminology 2 params → 200417404
GET
/api/v1/concept/{terminology}/associations/{codeOrLabel}
Get the association entries for the specified terminology and code.
getAssociationEntries 5 params → 417404200

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are Concept (31 properties), Mapping (23 properties), SearchCriteria (21 properties), AssociationEntry (14 properties). Each schema is shown below with its type and property counts.

HierarchyNode
object
Represents a node in a subtree rendering of the hierarchy
8 properties
Paths
object
Represents a list of paths
3 properties
AssociationEntry
object
Represents an entry in a table of associations between two concepts
14 properties
AssociationEntryResultList
object
6 properties
Property
object
Represents a type/value property on a concept
8 properties
Mapping
object
Represents a map from a concept to concepts in other terminologies
23 properties
Qualifier
object
Represents a type/value qualifier on a concept element
5 properties
History
object
Represents a history record, generally for a retired concept
8 properties
Concept
object
Represents a concept in a terminology
31 properties
Role
object
Represents a (logically) defining relationship between two concepts
10 properties
SearchCriteria
object
Criteria for a search or find operation
21 properties
ConceptMinimal
object
Represents minimal information about a concept in a terminology
7 properties
Path
object
Represents a path (or partial path) in a hierarchy
4 properties
Synonym
object
Represents one of the (potentially many) names for a concept
12 properties
Extensions
object
Generally unset, this is used for certain special cases
10 properties
Association
object
Represents a non-defining (in a logical sense) relationship between two concepts
10 properties
Definition
object
Represents a text definition for a concept
8 properties
DisjointWith
object
Represents an assertion of disjointness between two concepts
10 properties
RestException
object
Payload for JSON error responses
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cancer-gov-concept-endpoints-api-openapi.yml Raw ↑

Other APIs Cancer.gov publishes across the network.

NCI Clinical Trials Search API
AE Profile APIs.io
NCI Genomic Data Commons (GDC) API
AE Profile APIs.io
NCI Content Syndication Services
AE Profile APIs.io
Cancer.gov Diseases API
AE Profile APIs.io
Cancer.gov Interventions API
AE Profile APIs.io
Cancer.gov Terms API
AE Profile APIs.io
Cancer.gov Trials API
AE Profile APIs.io
Cancer.gov Application version endpoint API
AE Profile APIs.io
Cancer.gov Asset Details Controller API
AE Profile APIs.io
Cancer.gov Autosuggest API
AE Profile APIs.io
Cancer.gov Delete Collection Controller API
AE Profile APIs.io
Cancer.gov Delete Data File Controller API
AE Profile APIs.io
#Concept endpoints
← Back to C APIs
API Details
ID
cancer-gov:cancer-gov-concept-endpoints-api
Base URL
https://clinicaltrialsapi.cancer.gov/api/v2
Docs
https://clinicaltrialsapi.cancer.gov/
Provider
Cancer.gov
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cancer-gov-concept-endpoints-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cancer-gov-concept-endpoints-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cancer.gov Concept endpoints 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.