Skip to main content
Ingest keys (sl_public_…) are the credentials your services use to push OTLP telemetry — traces, logs, and metrics — to Superlog. You can manage them from the dashboard or automate minting with the management API. All endpoints on this page require a management key (sl_management_…). See Authentication for setup instructions. Base path: /api/v1/projects/:projectId/api-keys
Each ingest key is scoped to a single project. A key created for project A cannot send data to project B.

List ingest keys

GET /api/v1/projects/:projectId/api-keys Returns all ingest keys for the project — both active and revoked — ordered most-recently-created first.
Response
array
All ingest keys for the project.
string (UUID)
Unique identifier for the key.
string
Human-readable label assigned at creation.
string
The first few characters of the key (safe to display and log). Use this to identify a key without exposing the full secret.
string (ISO 8601) | null
When the key last authenticated a successful ingest request. null if the key has never been used.
string (ISO 8601) | null
When the key was revoked. null if the key is still active.
string (ISO 8601)
When the key was minted.

Mint an ingest key

POST /api/v1/projects/:projectId/api-keys Mints a new ingest key for the project. The full plaintext key is returned in the response and cannot be retrieved again — store it immediately.
Request body
string
A label for the key. Up to 120 characters. Optional — defaults to "API key" if omitted or blank.
Response
string (UUID)
Unique identifier for the key.
string
The name you provided (or the default "API key").
string
Stable prefix of the key, safe to store and display.
string
The full ingest key value. Pass this as Authorization: Bearer when sending OTLP data. Shown once only.
The plaintext value is returned exactly once. It is not stored in Superlog and cannot be recovered after this response. Copy it to a secrets manager or environment variable before discarding the response.

Key rotation workflow

Ingest keys cannot be revoked via the REST API — revocation is done from the Superlog dashboard under Settings → API Keys. Use the following pattern to rotate a key without dropping telemetry:
1

Mint a replacement key

Call POST /api/v1/projects/:projectId/api-keys with a descriptive name. Store the plaintext immediately.
2

Deploy the new key

Update your service configuration to use the new key. Verify that telemetry is flowing in the Superlog dashboard.
3

Revoke the old key from the dashboard

In the dashboard under Settings → API Keys, find the old key by its prefix and revoke it once all services have migrated.

Management keys

Management keys (sl_management_…) — the credentials used to call this API — are not manageable via the REST API. They are created and revoked exclusively through the Superlog dashboard under Settings → API Keys → Management Keys.
Give each management key a clear name that describes its consumer, such as Terraform module or GitHub Actions. This makes it easy to audit usage and revoke a specific key without disrupting others.