Skip to main content
Open Developers → SDK Credentials to manage OAuth clients for your workspace. Each credential has a client ID and a client secret. Your server exchanges these for a short-lived access token; the credential itself is not a bearer token.

​
Create a credential

  1. Check the workspace selected in the profile menu.
  2. Select New Credential.
  3. Copy the client ID and secret from the reveal dialog into your server’s secret store. The secret is shown only once.
  4. Give the credential a recognisable name using the edit control in its row, and select its environment.
  5. Follow Authentication to configure automatic token refresh or make a token request yourself.
The page includes integration snippets. Replace example context, event and item IDs with IDs from your workspace. Environment labels help your team identify credentials; they do not create separate datasets. Use separate workspaces when you need isolated data.

​
Manage existing credentials

The table shows each client’s name, ID, environment, creation date and revocation state. Use a different credential for each application so you can replace one without updating every service. If you lose a secret, create a new credential. For rotation, deploy the replacement, verify an authenticated request, then Revoke the old credential. Revoked credentials cannot obtain new tokens. Do not assume revocation invalidates every already-issued token immediately; tokens have their own expiry.

​
Choose the right credential

Never ship the client secret in a browser or mobile bundle. Keep Core API access in your backend; see SDKs for the integration options.