API Tokens

API tokens let you interact with Moneat's API programmatically. Use them in CI/CD pipelines to create releases, upload source maps, or build custom integrations. Tokens are scoped so you control exactly what each token can access.

Creating a token

  1. 1
    Navigate to token settings
    Go to Settings → API Tokens in the dashboard.
  2. 2
    Create a new token
    Click "Create Token" and provide a descriptive name (e.g., "CI/CD Pipeline", "Release Automation").
  3. 3
    Select scopes
    Choose the permissions your token needs. Only grant the scopes that are actually required.
  4. 4
    Copy and save
    Copy the generated token immediately. For security, the full token value is only shown once and cannot be retrieved later.
Save your token

The token is only displayed once when created. Store it securely in your CI/CD secrets or a password manager. If you lose it, you'll need to create a new token.

Token scopes

Scopes define what a token can do. Available scopes include:

  • releases:read - View releases and their details
  • releases:write - Create, update, and finalize releases
  • sourcemaps:read - List and download source map files
  • sourcemaps:write - Upload source maps and symbol files for symbolication
  • workflow:read - List workflows, runs, audit events, catalog entries, and usage
  • workflow:write - Create, update, publish, unpublish, and delete workflows
  • workflow:run - Start and cancel workflow runs

Additional scopes may be added as new API features are released.

Using tokens

API authentication

Include your token in the Authorization header with the Bearer scheme:

Shell
curl -H "Authorization: Bearer <your_token>" \
  https://api.moneat.io/api/0/organizations/{org}/releases/

With sentry-cli

Set the SENTRY_AUTH_TOKEN environment variable when using sentry-cli:

Shell
export SENTRY_URL=https://api.moneat.io
export SENTRY_AUTH_TOKEN=<your_token>
export SENTRY_ORG=<your_org>

sentry-cli releases new 1.0.0

Managing tokens

From the API Tokens settings page, you can:

  • Rename - Update the token's name
  • Update scopes - Add or remove permissions
  • Revoke - Permanently disable a token. This is immediate and cannot be undone.
Compromised tokens

If you suspect a token has been compromised, revoke it immediately and create a new one. Revocation takes effect instantly across all API requests.