API reference · Sales Rep Module
Manage Customer Portfolio in Bulk
- Method
- POST
- Route
-
/sellerModule/manageBulkWallet/:attendantInfo - Base URL
https://ws.autorei.net- Path parameters
:attendantInfo- Token
- Requires Bearer token
Opens this request in the public API documentation, the official source of the reference.
Description
Builds a sales rep's customer portfolio in bulk: links, unlinks, or replaces the customer list in a single call, instead of one request per customer.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
attendantInfo |
string | Yes | Identifies the sales rep in three ways: the UUID of the sales rep, the CPF/CNPJ of their account holder, or the email used to sign in. The route recognizes which one you sent. |
Request Body (JSON)
| Field | Type | Required | Description |
|---|---|---|---|
action |
string | Yes | BIND adds the customers to the portfolio, UNBIND removes them, REPLACE replaces the entire portfolio with the list sent. |
users |
array | Yes | Customers for the operation. Cannot be an empty list. |
| Customer identification | — | Yes | It is not a field — it is a group. In each item of users, send username or document. |
users[].username |
string | Conditional | Customer's sign-in email. Required if document is not sent. |
users[].document |
string | Conditional | CPF or CNPJ of the customer. Required if username is not sent. |
Do not send attendantId nor storeId: both are resolved by the backend, from the path and your token.
Business rules
Processing is asynchronous
The 200 response confirms that CWS received the list, not that the links were created. Processing happens in the background and there is no route to check the result — check the portfolio afterwards with GET /sellerModule/listCustomers/:id.
REPLACE deletes what is not in the list
With REPLACE, the portfolio becomes exactly the list sent: whoever was linked and does not appear in users is unlinked.
Response · 200
| Field | Type | Description |
|---|---|---|
status |
string | OK. |
message |
string | Os dados foram recebidos e o processamento será realizado em segundo plano. |
Errors
| Code | When |
|---|---|
| 400 | Missing body (Body não informado), action or users missing — including users empty — (Campos obrigatórios ausentes: action ou users.), action outside the list (O campo 'action' é inválido. Valores permitidos: BIND, UNBIND, REPLACE), item in users without username and without document (Todos os usuários devem conter pelo menos um dos campos: 'username' ou 'document'.), or sales rep not found by the form given in the path. |
| 401 | Token missing, malformed, or expired. |
Example request
curl --request POST 'https://ws.autorei.net/sellerModule/manageBulkWallet/:attendantInfo' \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: application/json' \
--data '{
"action": "BIND",
"users": [
{
"document": "29.893.264/0001-01"
},
{
"username": "contato@lojaexemplo.com.br"
}
]
}' Example responses
200Success — batch received for processing
{
"status": "OK",
"message": "Os dados foram recebidos e o processamento será realizado em segundo plano."
} Used in
- Use casesB2B customer portal: the typical path through the API
- Use casesGuided selling and counter sales: the typical path through the API
Related endpoints
Generated from the public API collection, published on 2026-09-04: api-docs.cws.digital.