Candid Health SDKs automatically handle authentication workflows after configuring them with the client_id and
client_secret.
Candid Health utilizes the OAuth 2.0 bearer token authentication scheme in our auth flow. You obtain the bearer token for all
subsequent API requests via the /auth/token endpoint defined below, which requires you to provide your client_id and client_secret. Your client_id and client_secret can be generated from the “Users & Credentials” tab by your org admin.
The bearer token is a signed JWT. The public key for the JWT can be found here for any verification workflows.
The bearer token should be provided in the Authorization header for all subsequent API calls.
The bearer token expires 5 hours after it has been created. After it has expired, the client will receive an “HTTP 401
Unauthorized” error, at which point the client should generate a new token. It is important that tokens be reused between
requests; if the client attempts to generate a token too often, it will be rate-limited and will receive an HTTP 429 Too Many Requests error.
Your application’s Client ID.
Your application’s Client Secret.
Time in seconds.