av_ and carries one or more scopes that control what it can access.
Scopes
| Scope | Description |
|---|---|
write | Required for all ingestion endpoints (/traces/batch, /otlp/v1/*) |
read | Required to verify a key with the ping endpoint |
List API keys
GET /me/api-keys/
Returns a paginated list of API keys for the authenticated user. The raw key value is never included in list responses.
Query parameters
Page number (1-indexed).
Number of keys per page.
Response
Array of API key objects.
Create an API key
POST /me/api-keys/
Creates a new API key and returns the full raw key value. Store it immediately.
Request body
A human-readable label to identify this key (e.g.
production-ingest). Optional but recommended.List of scopes to grant. Must contain at least one valid scope. Use
["write"] for ingestion.Organization slug to scope this key to. If omitted, the key is a personal key tied to your user account.
Response — 201
UUID of the new key.
Label you provided.
Scopes granted to this key.
Short prefix for identification in list views.
Always
true on creation.Organization slug or
null.ISO 8601 creation timestamp.
The full raw API key. Copy this now — it is never returned again.
Example response
Verify a key
GET /me/api-keys/ping/
Verifies that an API key is valid and has read scope. Useful for checking a key works before deploying.
Response — 200
Always
"ok" when the key is valid and has read scope.Revoke an API key
DELETE /me/api-keys/{key_id}/
Immediately revokes the key. Any subsequent requests using the revoked key receive 401.
Path parameters
UUID of the key to revoke.