Superlog Management API Reference

The Superlog Management API is a REST interface that lets you automate every aspect of your observability setup — from provisioning new projects and minting ingest keys to querying stored traces, logs, and metrics. All endpoints accept and return application/json.

Base URL

Environment	Base URL
Superlog Cloud	`https://api.superlog.sh`
Self-hosted	`https://<your-superlog-host>`

If you are on Superlog Cloud, your exact host URL is shown in your project settings page.

All management endpoints are served under the /api/v1/ path prefix. A machine-readable OpenAPI 3.1 spec is always available at /api/v1/openapi.json, and an interactive Scalar reference UI is at /api/v1/docs.

Authentication

Every request to /api/v1/* must carry an Authorization: Bearer header. Superlog uses two distinct key types — choose the right one for each use case.

Key type	Prefix	Scope	Used for
Management key	`sl_management_…`	Org-wide	All `/api/v1/*` REST endpoints
Ingest key	`sl_public_…`	Single project	OTLP data ingest (`/v1/traces`, `/v1/logs`, `/v1/metrics`)

See Authentication for step-by-step setup instructions.

Endpoint groups

Projects

List, create, and update projects in your org.

API Keys

Mint project-scoped ingest keys programmatically.

Telemetry Read

Query stored traces, logs, and metrics over REST.

OTLP Ingest

Send traces, logs, and metrics to Superlog from your services.

MCP Server

AI assistant integration for query_logs, query_traces, and more.

Error codes

Superlog uses standard HTTP status codes. Every error body follows the same shape:

{ "error": "human-readable message" }

Status	Meaning
`400 Bad Request`	Malformed or invalid request body / query parameters
`401 Unauthorized`	Token is missing, the wrong type, or has been revoked
`403 Forbidden`	Token is valid but does not have access to the requested resource
`404 Not Found`	Resource does not exist in your org
`409 Conflict`	A unique constraint was violated (e.g., a slug already in use)
`502 Bad Gateway`	An upstream call (e.g., to GitHub) failed
`503 Service Unavailable`	A required server-side integration is not configured

Content type

All request bodies must be JSON. Always include Content-Type: application/json when sending a body.

curl https://api.superlog.sh/api/v1/projects \
  -H "Authorization: Bearer sl_management_xxxx" \
  -H "Content-Type: application/json" \
  -d '{"name": "My App", "slug": "my-app"}'

​Base URL

​Authentication

​Endpoint groups

Projects

API Keys

Telemetry Read

OTLP Ingest

MCP Server

​Error codes

​Content type

Base URL

Authentication

Endpoint groups

Error codes

Content type