Skip to main content
POST
Send Event

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:

Path Parameters

definitionId
string
required

Identifier of the custom event definition. Event properties are passed in the request body.

personId
string
required

Identifier of the person who performed the event. The identifierType query parameter specifies the type of the ID.

Query Parameters

identifierType
enum<string>
required

Person's identifier type.

Available options:
ID,
EXTERNAL_ID,
PHONE,
EMAIL,
LINE,
FACEBOOK,
TELEGRAM,
PUSH,
WEB_PUSH,
LIVE_CHAT,
VIBER_BOTS,
INSTAGRAM,
INSTAGRAM_DM,
TWITTER,
APPLE_BUSINESS_CHAT,
KAKAO_SANGDAM,
GOOGLE_BUSINESS_MESSAGES,
WHATSAPP,
ZALO_FOLLOWER,
TIKTOK_BM
createPerson
boolean

Set this parameter to true to automatically create a person profile with the specified personId and identifierType if no existing profile matches the provided identifier. The default value is false.
Note: New profiles can only be created for the following identifier types: PHONE, EMAIL, or EXTERNAL_ID.

Body

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

Successfully created

eventId
string

Unique identifier of the event.

definitionId
string

Unique identifier of event schema.

occurredTime
string<date-time>

Time of event occurrence, as the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ

Example:

"2024-05-17T15:47:50.413Z"

properties
object | null

Object that contains event properties.

metadata
object | null

Object that contains metadata of event occurrence.