Skip to main content

API Keys Management

Manage API keys for your projects via the Developer API. API keys are scoped to individual projects and inherit the project’s security settings.

Endpoints

List API Keys

Retrieve all API keys for the authenticated user.
Headers:
Response (200 OK)
Full API key values are never returned in list responses. Use the Reveal endpoint to retrieve the full key.

Create API Key

Create a new API key for the current user.
Request Body
Response (201 Created)
The key field is only returned once during creation. Store it securely — you won’t be able to see it again.
Key limits by plan:

Delete API Key

Permanently delete an API key. This immediately revokes access.
Response (200 OK)

Toggle API Key Status

Enable or disable an API key without deleting it.
Response (200 OK)
Use toggle instead of delete when you want to temporarily disable a key (e.g., during incident response) without losing the key configuration.

Reveal API Key

Retrieve the full API key value. Use this to copy a key you’ve previously created.
Response (200 OK)

Code Examples

Error Responses

Best Practices

  1. Name keys descriptively — Use names like “Production Backend” or “Staging Cron Job” so you can identify them later
  2. One key per service — Don’t share keys between applications
  3. Rotate every 90 days — Create new key → update apps → delete old key
  4. Use toggle for incidents — Disable a compromised key immediately without losing the configuration
  5. Monitor last_used_at — Delete keys that haven’t been used in a while