The Users API contains all the endpoints needed to manage the user bases. You can use it to create, update or even search for users within certain parameters.
The /users/v1/ endpoint allows you to create a new user in our database.
The number of parameters required to create a user varies depending on the product you have signed up for, but we will always ask you for email and operation_country.
For the 'operation_country' and 'nationality' fields we expect a 3-character code respecting the ISO 3166 alpha-3 standard.
Here is a list of examples:
Each user must have a unique email, and the combination of identity document type and value must also be unique.
Acceptable identity documents are as follows:
In the case of the DNI, we will validate that its extension is 7 or 8 characters.
The accepted tax document type is:
In the case of CUIL, we will validate that the first two digits are 20, 23, 24, 27, 30, 33 or 34 and its length is exactly 11 characters
Acceptable identity documents are as follows:
The accepted tax document type is:
In the case of CPF, we will validate that its extension is exactly 11 characters.
Acceptable identity documents are as follows:
The tax document is not required, but the accepted type is:
In the case of the INE, we will validate that its extension is 9 or 13 characters.
Acceptable identity documents are as follows:
For CC we will validate that it has between 5 and 11 characters.
For CE we will validate that it has between 6 and 7 characters.
Para PPT validaremos que su extensión sea entre 1 y 8 caracteres.
The tax document is not required, but the accepted type is:
In the case of the NIT, we will validate that its extension is exactly 10 characters.
Acceptable identity documents are as follows:
For the DNI, we will check that its ID number is exactly eight characters long and all numeric
In the case of the CE or PASSPORT, we will validate that its extension is up to 12 alphanumeric characters.
The accepted tax document type is:
In the case of RUC, we will validate that the first two digits are 10, 15 or 17 and its extension is 11 digits.
Acceptable identity documents are as follows:
Validaremos que su extensión sea entre 8 y 12 caracteres, incluyendo el dígito verificador quel puede ser un dígito o una letra k.
The accepted tax document type is:
Validaremos que su extensión sea entre 8 y 12 caracteres, incluyendo el dígito verificador quel puede ser un dígito o una letra k.
If you operate in Argentina, the user’s legal address must be from one of these provinces:
If you operate in Brazil, you must fill out the zipcode
field with valid data, as we use it to determine the user's legal address.
If you operate in Mexico, there are no special requirements regarding the user's legal address fields.
In case the operating country is Chile, there are no special requirements regarding the user's legal address fields.
The /users/v1/ endpoint allows you to search for a group of users and receive a list sorted according to the parameters specified.
Filters must be specified as parameters following this pattern: filter[campo]=valor
. For example: /users/v1/?filter[status]=ACTIVE
To filter an attribute for several possible values, separate the values with commas.
Let's look at an example: filter[status]=ACTIVE,BLOCKED
The results are paginated and you can specify the amount of data per page and also which page to view using: page[number]=value and page[size]=value
You can specify the order of the results with certain parameters that you must send as list of strings in the sort filter type. For example: ?filter[status]=ACTIVE&sort=status,gender
The default sorting will be ascending. To specify a descending sorting, you must send the character '-' as a prefix of the attribute. For example: /users/v1/?filter[status]=ACTIVE&sort=status,-gender
The possible sorting attributes are:
id
gender
identification_type
identification_value
status
If a parameter is incorrect or misspelled, it will return an error.
The /users/v1/{id} endpoint allows you to query a user’s information through their user_id.
The endpoint /users/v1/{id} allows you to update a user’s information with their ID.
To block a user you must send the status
with the value BLOCKED
and the value CLIENT_INTERNAL_REASON
in the status_reason
field.
To reactivate a user you have blocked, you will need to send status
with value ACTIVE
.
Each user must have a unique email, and the combination of identity document type and value must also be unique.
Acceptable identity documents are as follows:
In the case of the DNI, we will validate that its extension is 7 or 8 characters.
The accepted tax document type is:
In the case of CUIL, we will validate that the first two digits are 20, 23, 24, 27, 30, 33 or 34 and its length is exactly 11 characters
Acceptable identity documents are as follows:
The accepted tax document type is:
In the case of CPF, we will validate that its extension is exactly 11 characters.
Acceptable identity documents are as follows:
The tax document is not required, but the accepted type is:
Acceptable identity documents are as follows:
For CC we will validate that it has between 5 and 11 characters.
For CE we will validate that it has between 6 and 7 characters.
Para PPT validaremos que su extensión sea entre 1 y 8 caracteres.
The tax document is not required, but the accepted type is:
In the case of the NIT, we will validate that its extension is exactly 10 characters.
Acceptable identity documents are as follows:
For the DNI, we will check that its ID number is exactly eight characters long and all numeric
In the case of the CE or PASSPORT, we will validate that its extension is up to 12 alphanumeric characters.
The accepted tax document type is:
In the case of RUC, we will validate that the first two digits are 10, 15 or 17 and its extension is 11 digits.
Acceptable identity documents are as follows:
En el caso del RUT, validaremos que su extensión sea entre 8 y 12 caracteres, incluido el digito verificador, el cual puede ser un dígito o una letra k.
The accepted tax document type is:
En el caso del RUT, validaremos que su extensión sea entre 8 y 12 caracteres, incluido el digito verificador, el cual puede ser un dígito o una letra k.
If you operate in Argentina, the user’s legal address must be from one of these provinces:
If you operate in Brazil, you must fill out the zipcode
field with valid data, as we use it to determine the user's legal address.
If you operate in Mexico, there are no special requirements regarding the user's legal address fields.
In case the operating country is Chile, there are no special requirements regarding the user's legal address fields.