Skip to main content
v1 sunsets December 31, 2026. Migrate to v2 — see the migration guide.
To access the v1 APIs, authentication via Bearer tokens is required. These tokens are generated by creating API keys through the dashboard. Once generated, signing the keys allows access to the APIs with the assigned scopes.

Generating a JWT bearer token

Once an API key is created, a JWT bearer token can be generated by signing the key. The token is then used to authenticate requests to the APIs. To generate a JWT bearer token, sign an API key using the ES256 algorithm, along with the name and privateKey from the downloaded API Key JSON file. The following snippets show how to create a JWT bearer token in various languages.
Run the code to generate the JWT bearer token.
Retrieve the organization ID from the orgId parameter and the private key from the privateKey parameter in the JSON file downloaded during API key creation.

Using the JWT bearer token

Once the JWT bearer token is generated, include it in the Authorization header of each request. Example using cURL:
Replace {JWT_Bearer_Token} with the generated token.
  • JWT bearer tokens expire 2 minutes after generation. A new token must be generated for continued API access.
  • Setting a longer expiry time using exp is not allowed.
  • A unique JWT must be generated for each API request; reuse of tokens is not permitted.
Need idempotent state-changing requests? The Idempotency-Key header is not supported on v1 — it is available on v2 and v3. See /v2/authentication and /v3/idempotency.