Authorizations
Authentication header of the form Bearer: <token>, where <token> is either your public or private API key. See when to use which
Body
The ID of the user as defined in your own application
"d34daa11-3745-4ac0-880e-d4b4d51fe13f"
Optional properties to add to the user
{
"email": "john@doe.com",
"firstName": "John",
"lastName": "Doe",
"imageUrl": "https://example.com/john-doe.jpg"
}If set to true, the user will automatically complete any eligible Flows with completionCriteria that have not already been completed. This is useful if a Flow has been recently updated with new steps and you want to ensure that historic users complete the new steps
Optional tracking events to add to the user
[
{
"event": "SignedUp",
"properties": {
"source": "landing-page",
"campaign": "summer-sale"
}
}
]Merges a guest with a non-guest user. Only works if the provided linkGuestId is a guest user and the userId does not yet have any state in any Flows.
Response
The user has been successfully created or updated