Skip to main content
POST
Identify
Stale data rejection: Vero compares a timestamp against when each property was previously updated and rejects outdated changes. Provide 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

auth_token
string
query
required

Body

application/json
id
string

The unique identifier of the customer.

Example:

1000

email
string

The email of the customer.

Example:

"test@example.com"

channels
object[]

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.

data
object

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.

Example:
extras
object

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.

Response

OK

status
integer<int32>
Example:

200

message
string
Example:

"Success."