Skip to main content
POST
Ingest a customer event or claim
Accept one consented activity event. Idempotency-Key is required. Returns 202 after durable accept. Profile reads see the event after status is processed. See events and intents.

Authorizations

Authorization
string
header
required

OAuth 2.1 authorization code with PKCE. Implicit and password flows are unsupported.

Headers

Idempotency-Key
string
required

Required for mutating requests. Replays with the same key and payload hash return the original logical result; replays with a different payload hash return 409.

Required string length: 16 - 255
X-Request-Id
string

Optional caller-supplied correlation ID echoed in responses and errors.

Body

application/json
customer_id
string
required
client_event_id
string
required

Partner-generated event ID used alongside the idempotency key.

event_type
string
required
Example:

"purchase.completed"

ontology
string
required
Example:

"ygo"

Available options:
account_linking,
personalization,
analytics,
support,
event_enrichment,
profile_resolution,
measurement
occurred_at
string<date-time>
required
payload
object
required
ontology_category
enum<string>
Available options:
outcome,
sentiment,
affiliate,
habit,
activation
object
string

Catalog or intent object the event is about, such as an entry_id or SKU.

Example:

"sku_blue_eyes_tin"

context
object
confidence
number
default:1
Required range: 0 <= x <= 1
provenance
object

Response

Event accepted for processing.

event_id
string
required
status
enum<string>
required
Available options:
accepted,
duplicate,
replayed
accepted_at
string<date-time>
required
sequence
integer
Required range: x >= 0
processing_status
enum<string>
Available options:
queued
workflow_id
string