IDC User Guide

Accessing the API

The following characteristics apply to all IDC APIs:
  • You access a resource by sending an HTTP request to the IDC API server. The server replies with a response that either contains the data you requested, or a status indicator.
  • An API request URL has the following structure: <BaseURL><API version><QueryEndpoint>?<QueryParameters> For example, the URL shown below is a request for metadata on all collections in IDC data version 1.0. curl -X GET "" -H "accept: application/json"

API Endpoints

Some of the APIs, such as the data_models and /cohorts/preview APIs, can be accessed without authorization. APIs that access user specific data, such as cohorts, necessarily require account authorization.
To access these APIs that require IDC authorization, you will need to generate a credentials file. To obtain your credentials:
  • Clone the IDC-Examples git repository to your local machine.
  • Execute the script either through the command line or from within python. Refer to the file for detailed instructions.
Example usage of the generated authorization is demonstrated by code in the How_to_use_IDC_APIs.ipynb Google Colab notebook.

Paged queries

Several IDC APIs, specifically /cohorts/manifest/preview, /cohorts/manifest/{cohort_id}, /cohorts/query/preview, /cohorts/query/{cohort_id}, and /dicomMetadata, ar_e paged. That is, several calls of the API may be required to return all the data resulting from such a query. Each accepts a _page_size query parameter that is the maximum number of objects that the client wants the server to return. The returned data from each of these APIs includes a next_page value. next_page is null if there is no more data to be returned. If next_page is non-null, then more data is available.
There are corresponding queries, /cohorts/manifest/nextPage, /cohorts/query/nextPage, and /dicomMetadata/nextpage, endpoints that each accept two query parameters: next_page, and page_size. In the case that the returned next_page value is not null, the corresponding ../nextPage endpoint is accessed, passing the next_page token returned by the previous call.


The manifest and query endpoints may return an HTTP 202 error. This indicates that the request was accepted but processing timed out before it was completed. In this case the client should resubmit the request including the next_page token that was returned with the error response.