Create User

Create user profiles programmatically via the API instead of the widget. When a user is created through this endpoint, light KYC (LKYC) verification happens automatically behind the scenes. This streamlines the onboarding flow so that when end-users subsequently open the widget, they can skip identity verification and proceed directly to entering payment information or completing checkout, significantly reducing friction and increasing conversion rates. Additionally, this endpoint allows you to capture the user_id directly from the response payload and store it immediately in your own database for seamless cross-system reconciliation. Contact our support team to request this feature for your Partner ID.

Endpoints


EnvironmentMethodEndpoint
SandboxPOSThttps://partner-sandbox.wert.io/api/external/users/create
ProductionPOSThttps://partner.wert.io/api/external/users/create

Limits

‼️

Important!

  • Your users must agree to share their personal data with Wert.
  • Non-English characters should be standardized to English before passing to the API.

Body


has_accepted_terms_of_service
boolean Required

Indicates whether the user has accepted the terms of service.

Possible values: true, false


phone
string Required

The user's phone number with country code.

Possible values: For example, +1234567890


email
string Required

The user's email address.

Possible values: For example, [email protected]


first_name
string Required

The user's first name.

Possible values: 2–30 characters; A-Z, a-z, 0-9; No special characters (?, @, #, $, etc.); Cannot be all numeric.


middle_name
string Optional

The user's middle name.

Possible values: 2–30 characters; A-Z, a-z, 0-9; No special characters (?, @, #, $, etc.); Cannot be all numeric.


last_name
string Required

The user's last name.

Possible values: 2–30 characters; A-Z, a-z, 0-9; No special characters (?, @, #, $, etc.); Cannot be all numeric.


date_of_birth
string Required

The user's date of birth.

Possible values: YYYY-MM-DD, for example 1990-01-01.


country_of_residence
string Required

The user's country of residence.

Possible values: Click to see alpha-3 country code, for example DEU, USA, RUS.


state_of_residence
string Required

The user's state of residence.

Possible values: Click to see alpha-2 US state code, for example AZ, AK, CA.


tin
string Optional

Taxpayer Identification Number. For USA, a Social Security number: dashes and spaces are ignored, and exactly 9 digits are stored as 000-00-0000. For any other country, the trimmed value is stored as given. A blank value is rejected. The value is not returned.

Example Request


curl -X POST '[https://partner.wert.io/api/external/users/create](https://partner.wert.io/api/external/users/create)' \
 -H 'X-Api-Key: your-unique-api-key' \
 -H 'Content-Type: application/json' \
 -d '{
   "has_accepted_terms_of_service": true,
   "phone": "+1234567890",
   "email": "[email protected]",
   "first_name": "John",
   "middle_name": "Paul",
   "last_name": "Doe",
   "date_of_birth": "1990-01-01",
   "country_of_residence": "USA",
   "state_of_residence": "CA",
   "tin": "000-00-0000"
}'

Response


created_at
string

Timestamp of when the user was created (UTC).

Possible values: 2026-06-02T08:44:43.000Z


user_id
string

The unique identifier for the created user in Wert's database.

Possible values: 01KT3R3BQ2ZRBHZN58E6VVY5F3

Example Response


{
    "created_at": "string",
    "user_id": "string",
}

References


User Create Errors

Refer to user creation error codes for more details.

{
    "field": "phone",
    "message": "Invalid phone format"
}
{
    "field": "email",
    "message": "Invalid email format"
}
{
    "field": "date_of_birth",
    "message": "Invalid date_of_birth format"
}
{
    "field": "first_name",
    "message": "Invalid first_name format"
}
{
    "field": "country_of_residence",
    "message": "Invalid country_of_residence format"
}
{
    "field": "tin",
    "message": "Invalid tin"
}

User Create Error Codes

Error CodeDescription
400Bad request. Ensure all required fields are present and meet validation criteria.
401Unauthorized. Check your API key or contact support.
403Forbidden. Ensure the user is 18+ years old, country and state are supported, and the user has accepted the terms and conditions.
409Conflict. A user with the same phone number may already exist.
429Too Many Requests. Retry later.
500Internal Server Error.

Did this page help you?