Skip to main content
POST
Ingest a batch of CDP events

Authorizations

Authorization
string
header
required

Dashboard JWT token from Clerk

Headers

Idempotency-Key
string

Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.

Required string length: 1 - 255
X-Test-Mode
enum<string>

Sandbox opt-in for Clerk-session-authenticated requests — see Test mode explained for the full credential-header matrix and worked samples. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.

Available options:
true,
false

Path Parameters

ingest_id
string
required

Body

application/json
batch
object[]
required

Up to 200 events, each a track / identify / page / screen / group / alias item carrying its own type field.

Maximum array length: 200
Example:
context
object

Shared Segment context applied to every item.

Example:
sentAt
string<date-time>

When the batch was sent (ISO 8601).

Example:

"2026-10-11T09:25:00.000Z"

Response

The batch acknowledgement — received, the processed count, and the ordered per-item results — in the standard { data, meta } envelope.