Skip to main content
Custom API keys let you create additional tokens beyond your main account key. Each token can have its own budget, expiration, and type, giving you fine-grained control over access and spending.

Use Cases

  • Environment separation — dedicated keys for development, staging, and production
  • Team access — separate keys for different team members or projects
  • Budget control — set credit limits per key to cap spending
  • Security — rotate or revoke individual keys without affecting other integrations
  • Usage tracking — monitor consumption per key

Token Types

Sandbox tokens return simulated responses and do not incur any cost. They are ideal for development and CI pipelines.

API Endpoints

Create a Token

Create a Token with Budget

Set a spending limit by enabling active_balance:
When active_balance is true, every API call deducts from the token’s balance. Once it reaches $0, the token stops working.

List All Tokens

Best Practices

Use clear naming conventions like env-project-purpose (e.g., prod-billing-api, dev-ml-team) so tokens are easy to identify at a glance.
  • Set budgets on non-production tokens to prevent accidental overspending during development.
  • Use sandbox tokens for CI/CD to validate integrations without incurring costs.
  • Rotate tokens periodically — create a new token, migrate your application, then delete the old one.
  • Set expiration dates on temporary tokens (e.g., for contractors or short-term projects).