Digital Science APIs support two complementary authentication schemes:

• API Keys – the quickest way to get started.
• JWT (JSON Web Tokens) – best for production workloads and delegated access.

Choose whichever fits your deployment or combine them as needed.

API Keys

Digital Science APIs use API keys for authentication. Visit your API Keys page to retrieve the API key you'll use in your requests.

Remember that your API key is a secret! Do not share it with others or expose it in any client-side code (browsers, apps). Production requests must be routed through your own backend server where your API key can be securely loaded from an environment variable or key management service.

All API requests should include your API key in an HTTP header as follows:

X-API-KEY: $API_KEY
GET /v1/ping HTTP/1.1
Host: api.digital-science.com

JWT tokens

Our API uses JWT (JSON Web Tokens) for authentication. JWTs allow secure communication between your application and our API, ensuring that only authorized users can access protected resources.

To access protected endpoints, you must include a valid JWT token in the Authorization header of your HTTP requests.

Use “Public Keys“ page in Developer Portal to create a public key and configure its access to the services behind.

There are instructions on how to generate and use JWT tokens available.

Authentication: $JSON_WEB_TOKEN
GET /v1/ping HTTP/1.1
Host: api.digital-science.com