Authentication and Headers

Authentication

Authentication with the Platform APIs are token-based. Ensure that all requests carry the token in the Authorization header as shown below:

'Authorization: Token <PASTE_YOUR_TOKEN>'

Headers

Requests to the platform APIs must contain the following additional headers:

1. Source header: User identification is done through the Source header. Ensure that all requests carry the Source header as shown below:

   'Source: <PASTE_YOUR_SOURCE>'

2. Content-type header: All requests with a payload in the request body (such as POST, PUT, and PATCH calls) must include a Content-Type header.

   Commonly supported values are:

   application/dicom

   multipart/form-data

   multipart/related etc.

   The appropriate Content-Type value should be selected based on the specific requirements of the API you are interacting with.

3. User-Agent header: The User-Agent header is necessary to identify the client software making the request. Ensure that all requests include an appropriate User-Agent header to avoid potential errors. An example is shown below:

   'User-Agent: <YOUR_USER_AGENT>'