Skip to main content
Every route under /v1 requires an API key in the Authorization header using the Bearer scheme.
Never send an API key in a URL, query parameter, source code, or support message. Treat it like a password.

Create a key

  1. Go to Settings → Advanced → API Keys.
  2. Select Create API key.
  3. Choose a name that identifies the consumer, such as Leme or Claude Code.
  4. Keep the key read-only to query the resources available in this version.
  5. Copy and store the secret immediately. It will not be displayed again.
Only organization owners and administrators can manage API keys.

Use the key

Store the credential in your platform’s secret manager or in a local environment variable:
Then send the header with every request:

Scopes

Always use the least privilege required. A read key is enough for Leme and agents that only query data.

Revoke a key

Immediately revoke a key that has been exposed or is no longer used. On the API Keys page, select the credential and confirm Revoke. Subsequent requests receive 401 authentication_error.