Events

Events ingestion.

Send an event

post

Reports an event that occurred for a specific contact.

The payload must include the contact identifier (contact.id). If this is the first time you report this contact, you must also provide at least one reachable identifier: contact.phone or contact.email.

You can report events for contacts that do not yet exist in Pristo. In that case, Pristo will create the contact and add it to the population. If the contact already exists, its details will be updated according to the contact data you send.

For the contact, you can send built-in fields or custom fields. Built-in contact fields: id (required), email, phone, language, name, lastName. Custom contact fields are fields you define on your population (e.g., gender, age) and are sent under contact.customFields.

For the event itself, you can send built-in fields or custom fields. Built-in event fields: type (required; must be defined in Pristo), occurredAt (optional timestamp). Custom event fields are fields you attach to events (e.g., channel, purchaseAmount, transactionId) and are sent under customFields. All custom field values must be strings and are limited to 50 characters.

Authorizations
X-API-KeystringRequired

API key (UUID)

Path parameters
populationIdstring · uuidRequired

Population identifier (UUID)

Header parameters
X-Request-Idstring · uuidOptional

Optional request correlation ID

Body
typestringRequired

Event type identifier

occurredAtstring · date-timeOptional
Responses
chevron-right
201

Event stored

application/json
eventIdstring · uuidOptional
receivedAtstring · date-timeOptional
post
/v1/events/send/{populationId}

Last updated