Skip to main content
The Prizm REST API authenticates every request with a bearer token — a JWT you generate from your organization’s settings.
Prizm issues two distinct token types: API access tokens (for REST integrations like this API) and MCP access tokens (for MCP clients such as Claude Desktop or Cursor). They are not interchangeable — an MCP token will not authenticate REST API calls. This page covers API access tokens only.

​
Generate a token

1

Open Access Tokens

In Prizm, go to Settings → Organization → Access Tokens and click Add token.
2

Configure the token

Set:
  • Key alias — a descriptive name, for example reporting-integration
  • Generated for — select API
  • Expiry — choose an appropriate expiration date
3

Copy the token

After creating the token, copy it from the table. For API tokens, this is a plain JWT string — copy it now, since it’s shown only once.
Store the token as a secret (environment variable, secrets manager, or your platform’s equivalent). Never commit it to source control.

​
Using the token

Send the token as a Bearer token in the Authorization header of every request. Do not send it as a custom header or query parameter.

​
Generating a token via the API

You can also create an API access token programmatically, using an existing session or API token:
generated_for is what distinguishes an API token from an MCP token — always set it to "API" when generating a token for REST use.

​
Token reference

​
Token errors

A complete list of error response shapes and codes is still being documented — see Response & Error Format for what’s confirmed so far.