Skip to main content
POST
Batch Send Events

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Body

definitionId
string
required

Unique identifier of event schema.

occurredTime
string<date-time>
required

Time of event occurrence, as the following format yyyy-MM-dd'T'HH:mm:ss.SSSZ. Events occurred more than 30 days ago will be rejected. Future dates are not allowed and will be automatically set to the current UTC time.

Example:

"2025-03-17T13:00:27.864Z"

identifier
object
required

Used to match the event to an existing person profile using the provided identifier.
If no matching profile is found, a new profile will be automatically created.
Note: New profiles can only be created for the following identifier types: PHONE, EMAIL, or EXTERNAL_ID.

eventId
string | null

Unique identifier of the event. If provided, it helps prevent duplicate events in case of retries—for example, if the first API call fails and the same event is sent again. Passing the same eventId ensures the event is only recorded once in the person profile.
The value must be 1–36 characters long and can include letters (A–Z, a–z), digits (0–9), underscores (_), and hyphens (-) only.

properties
object | null

Object containing event properties. Must match the corresponding event definition. See People Events documentation for supported data types.

Response

Accepted