Skip to main content
The ingest API accepts batches of canonical events over HTTPS. The SDK uses it under the hood; use it directly from any language that can send JSON.

​
Base URL

​
Authentication

Authenticate every request with an API key as a bearer token:
Create keys in the dashboard under Settings → API Keys — see API keys. The key determines the space your events land in. Requests with a missing, malformed, or revoked key return 401.

​
Request limits

Requests over either limit return 413. Split large workloads into multiple batches.

​
Errors

Every error response has the same shape:

​
Retries

  • Retry on 5xx, 503, and network failures, with backoff.
  • Do not retry 400, 401, or 413 — fix the request instead.
  • Reuse the same event id values when retrying. Events are deduplicated by ID, so retries never create duplicates — see Delivery guarantees.

​
Success

A successful request returns 202 Accepted: events are validated and durably queued, and will appear in the dashboard within seconds. See POST /v1/ingest-events.