identify and track, in any mix — each applied as its own endpoint would apply it, in order. One that can’t be applied doesn’t stop the rest.
Server events need the OMNI API and Customer data in your plan, and an OMNI API key — not a Customer data source key (sk_live_…), which is now refused.
Needs the
cdp.events:write scope.Body
Each event is the body of POST /v1/identify or POST /v1/track, with a
type:
Send an
Idempotency-Key header to take it once however often the request is retried.
Events are applied in the background, so the answer only says how many were taken. One that can’t be applied — no one named, a reserved event name, properties too large — is dropped without stopping the rest, and shows with its reason under Live events on Settings → Data sources in the panel.
Request
Response
202 Accepted — accepted is how many events were taken, to be applied in the background.
Errors
Every refusal is{"error": {"code", "message", "field"}}; field is there when one input is at fault.
Any request can also be refused for its key, its account or its rate (
key_required, invalid_key, account_suspended, plan_excludes_api, address_not_allowed, rate_limited); see the overview.