Developers

API Reference

Documented endpoints that exist today for ingest, session app queries, and API-key trace listing. Prefer first-party SDKs when available.

Ingest

POST /api/rum/v1/ingest — browser RUM (Browser SDK, publishable pk_live_…).
POST /api/logs/v1/ingest — structured logs (Logs SDK, secret / source token).
POST /api/traces/v1/otlp — OTLP HTTP traces (OpenTelemetry).

App (session)

Authenticated browser session required:

GET /api/app/traces/search
GET /api/app/correlation
GET /api/app/logs/search
GET /app/logs/export — export from the authenticated app (not an ingest token).

Public API keys

GET /api/v1/traces — list traces with a workspace API key (Bearer). See API Keys.

Auth notes

Never put secret keys or log/trace tokens in browser code. RUM ingest rejects secret-style keys. Session app routes use the signed-in workspace; do not trust a client-supplied workspace id.

Limitations

This guide documents only the endpoints above — do not assume other paths from older marketing copy.
Entitlements (logs, tracing, API access) still apply per plan.