Update customer with the Asaas API
Updates a customer. Fields not sent stay as they are.
- Identifier
- asaas_update_customer
The request
POST https://connect.reportei.com/api/tools/asaas_update_customer/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"id": "<id>"
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | Yes | Id of the customer, starting with cus_, from List customers or Create customer. |
| name | string | No | Name of the customer, a person or a company. |
| cpfCnpj | string | No | CPF or CNPJ of the customer, digits only. |
| string | No | Email address where Asaas sends the payment notifications. | |
| mobilePhone | string | No | Cell phone with area code, digits only, for example 11999998888. |
| phone | string | No | Landline with area code, digits only. |
| postalCode | string | No | CEP of the address, for example 01310-000. |
| address | string | No | Street of the address. |
| addressNumber | string | No | Number of the address. |
| complement | string | No | Complement of the address. |
| province | string | No | Neighborhood of the address. |
| company | string | No | Company of the customer. |
| additionalEmails | string | No | More email addresses for the payment notifications, separated by commas. |
| groupName | string | No | Name of the group to put the customer in. |
| externalReference | string | No | Identifier of the customer in your own system. |
| observations | string | No | Internal notes about the customer. |
| notificationDisabled | boolean | No | true stops Asaas from sending payment notifications to this customer. |
Supported connections
Your customer connects their Asaas account once, with one of the modes below. The same connection serves every tool of the toolkit.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/asaas_update_customer. It becomes your agent's tool definition with no conversion.
Other Asaas tools
- List customersGETLists the customers (payers) of the account, optionally filtered by name, email, CPF or CNPJ, group or external reference. The response has data, totalCount and hasMore; page with offset and limit while hasMore is true.
- Get customerGETReturns one customer, with name, CPF or CNPJ, email, phones, address and notification setting.
- Create customerPOSTCreates a customer, the payer of payments and subscriptions. name and cpfCnpj are required. There is no city field: Asaas takes the city from postalCode.
- List paymentsGETLists the payments (cobrancas), optionally filtered by customer, subscription, status, billing type, payment date or external reference. Values are in reais. The response has data, totalCount and hasMore; page with offset and limit while hasMore is true.
- Get paymentGETReturns one payment, with status, value, net value, due date, payment date and the links invoiceUrl (the payment page) and bankSlipUrl (the boleto).
- Create paymentPOSTCreates a payment (cobranca) for a customer, by boleto, Pix or credit card, one-time or in installments. The response has invoiceUrl, the payment page to send to the payer, and Asaas may notify the customer according to the customer notification settings.
- Update paymentPUTUpdates a payment that is still pending or overdue; the customer cannot change. Send billingType, value and dueDate even when they stay the same, with the current values from Get payment. A new value or due date may notify the customer.
- Delete paymentDELETERemoves a payment, which can no longer be paid; it can be restored in Asaas. It does not refund an amount already paid, and removing a payment of a subscription does not end the subscription.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.

Conta Azul