Release operations
Use a surface secret key withrelease:write. Send it as a bearer token or in the x-api-key header.
INTERFERE_API_KEY to the secret key from your surface. Run secret-key requests from your server or build environment.
Ingestion operations
Use the surface’s public key for endpoints that accept public-key authentication. The SDK supplies it for normal application capture. Check the operation’s authentication fields before making a direct request. For native OTLP ingestion at/drain/v1/traces, /drain/v1/logs, and /drain/v1/metrics, use a workspace key with org:telemetry:write. Send it as Authorization: Bearer <key> or in x-api-key. See OpenTelemetry ingestion.
Workspace automation
Use MCP or the CLI to work interactively with workspace data. Use scoped workspace keys for unattended operations and Terraform to manage infrastructure configuration.Authentication errors
A401 response means the request needs a valid credential. Check the key, its expiration, and the authentication method accepted by the operation.
For 403, check the credential’s scopes, its creator’s current workspace access, and the workspace’s network rules.