For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

The IDC API provides programmatic access to IDC metadata and data: discover what is in IDC, build cohorts with attribute filters, retrieve download manifests, run read-only SQL queries, explore clinical data, and generate citations and license summaries for your selections.

The API is live in production at:

https://api.imaging.datacommons.cancer.gov/v3

All IDC data is public and open β€” no authentication, account, or credentials are required to use the API.

The current API release is version 3 (v3), in beta. The /v3 contract may still change in response to feedback before the final 3.0.0 release. To see exactly which beta build is deployed, call GET /v3/version β€” the api_version field reports the running release. If you have feedback, please let us know on the IDC support forum!

Explore every endpoint interactively in the Swagger UI, or fetch the machine-readable OpenAPI specification.

Writing the calls yourself is only one way in β€” the same capabilities are also exposed as agent tools. If you would rather have an AI assistant do the querying, see Using IDC with an AI assistant.

What you can do

  • Discover what's in IDC β€” collections, derived analysis results (segmentations, annotations), filterable attributes and their valid values, headline statistics.

  • Build cohorts β€” turn attribute filters into distinct patient/study/series counts, a page of matching series, and a ready-to-use download payload.

  • Retrieve β€” public s3:// URLs, a full manifest.txt, and idc CLI commands; files transfer directly from public S3/GCS buckets, never through the API server.

  • Run SQL β€” guarded read-only queries against the series-level index table, specialized per-modality indices, and per-collection clinical tables β€” joins, aggregations, anything the structured filters can't express.

  • Explore clinical data β€” discover and read the per-collection clinical tables (demographics, staging, therapies, outcomes) and join them to imaging.

  • Publish responsibly β€” viewer URLs for visual inspection, per-cohort license breakdowns (CC BY vs CC BY-NC), and ready-to-use citations.

In this section

The API is developed in the open at ImagingDataCommons/IDC-REST-MCP, which also hosts the developer-facing documentation.

Last updated

Was this helpful?