Create User Account (v3)
POST/v3/users/accounts
Create an user account. User account is a base for all other entities. It must be created as first entity.
Changed in v3 (compliance/KYC required data):
emailis now required for every payload. Sending onlyphone_numberis no longer accepted.birth_dateis now required forNATURAL_PERSONpayloads.issue_dateis now required forLEGAL_PERSONpayloads.
Version 2 keeps accepting the previous, looser payload and is deprecated.
Request
Header Parameters
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
- application/json
Body
required
Create user account payload.
- Natural Person
- Legal Person
- female.
- male.
- non_binary.
- other.
- prefer_not_to_say.
- NATURAL_PERSON.
- LEGAL_PERSON.
- NATURAL_PERSON.
- LEGAL_PERSON.
- EI.
- MEI.
- EIRELI.
- SLU.
- LTDA.
- SA.
- SS.
- COOP.
- OTHER.
User short name or company trade name.
User full name or company name.
Possible values: [male, female, non_binary, other, prefer_not_to_say]
User gender:
User mother name.
User birth date. Required for NATURAL_PERSON payloads, not allowed for LEGAL_PERSON ones.
User CPF or company CNPJ, without mask. The CNPJ may be alphanumeric.
User or company phone number.
User or company e-mail.
User should start as active?
Possible values: [NATURAL_PERSON]
Person type:
User short name or company trade name.
User full name or company name.
Company document issue date. Required for LEGAL_PERSON payloads, not allowed for NATURAL_PERSON ones.
User CPF or company CNPJ, without mask. The CNPJ may be alphanumeric.
User or company phone number.
User or company e-mail.
User should start as active?
Possible values: [LEGAL_PERSON]
Person type:
Possible values: [EI, MEI, EIRELI, SLU, LTDA, SS, SA, COOP, OTHER]
Legal type:
Responses
- 201
- 400
- 401
- 403
- 409
- 422
User account created.
- application/json
- Schema
- Example (from schema)
Schema
User account ID.
Possible values: [pending, active, expired, deactivated, deleting]
User state.
User created date.
{
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"state": "active",
"created_at": "2026-10-27T17:48:17.113Z"
}
If any required params are missing or has invalid format or type.
User authentication failed.
If the authenticated user does not have permission.
If the provided user id is already in use, if a user account with the same document is already registered for this product, or if the email or phone number is already in use.
If any required params are missing or has invalid format or type.