Submit a named event asynchronously
Submits a specific named consumer event asynchronously. The event name is supplied in the URL path and the body is an open data map. No per-request rate limit. Returns event_id only; person identification occurs asynchronously.
Authorizations
Path Parameters
Body
Open map of fields submitted with an event. May include keys beyond those listed here. email is the primary identity key and the only field that enables profile merging. partner_user_id is a secondary lookup key and is not guaranteed unique.
Primary identity key. The only data-map field that enables profile merging when submitted.
"user@example.com"
ISO 8601 timestamp of when the event occurred. Optional; defaults to the time the request is received. Use for backdated events. On wrapped request bodies this is an alternative to the top-level event_time field.
"2024-01-15T12:00:00Z"
Secondary lookup key for an existing profile. Not guaranteed unique across your program.
"usr_8392047156"
Extole person identifier. Numeric. Submit to target an existing profile instead of resolving by email or partner user id.
7465313346145957000
Response
Event accepted and queued for asynchronous processing. Returns the assigned event_id. Person identification completes after the response is returned.
Unique identifier for the queued event. Person identification occurs asynchronously after the request returns.
