POST
Authorization
All you need is to include your secret key as a value of authorization in the header and hit the endpoint above. Use the secret key that matches the mode you are in TEST or LIVE
Request Body
Provide the user’s email address and optionally include their name and country code. The email address of the user. Must be a valid email format.
The name of the user (optional)
A 2-letter ISO country code (e.g., “US”, “GB”, “FR”). Must be uppercase or will be converted to uppercase.
Users are unique per project and mode combination. The same email can exist in both TEST and LIVE modes.
Response
If the user is created successfully, you will receive an object containing the user’s details.Error Responses
400 Bad Request - Missing Body
400 Bad Request - Missing Body
Returned when the request body is missing or empty.
400 Bad Request - Missing Email
400 Bad Request - Missing Email
Returned when the email field is not provided.
400 Bad Request - Invalid Email
400 Bad Request - Invalid Email
Returned when the email format is invalid.
400 Bad Request - Invalid Country Code
400 Bad Request - Invalid Country Code
Returned when the country code is not a valid 2-letter code.
400 Bad Request - Invalid JSON
400 Bad Request - Invalid JSON
Returned when the request body contains malformed JSON.
409 Conflict
409 Conflict
Returned when a user with the same email already exists in this project and mode.
500 Internal Server Error
500 Internal Server Error
Returned when an unexpected error occurs.