Identify
This endpoint creates a new user profile if the user doesn’t exist yet. Otherwise, the user profile is updated based on the properties provided.
created_at in extras to set this timestamp explicitly; if omitted, the time the request was received is used. This helps prevent out-of-order updates from overwriting newer data.Update only: If you include update_only set to "true" in extras, Vero updates an existing user profile but does not create a new profile if the user does not exist.Authorizations
Body
The unique identifier of the customer.
1000
The email of the customer.
"test@example.com"
A valid JSON array containing hashes of key/value pairs that represent the user's device token. Each hash should represent a single device token and include the fields type, address, and platform.
A valid JSON hash containing key value pairs that represent the custom user properties you want to update. The language, timezone and userAgent attributes are reserved properties that may be updated automatically by our SDKs. You can use these properties but bear in mind they may be overwritten if using our SDKs or integrations. All other keys are freeform and can be defined by you.
A valid JSON hash containing key/value pairs that represent the reserved, Vero-specific created_at and update_only properties. Refer to the note above.

