Create customer with the Asaas API

Creates a customer, the payer of payments and subscriptions. name and cpfCnpj are required. There is no city field: Asaas takes the city from postalCode.

Identifier
asaas_create_customer

The request

POST https://connect.reportei.com/api/tools/asaas_create_customer/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "name": "<name>",
    "cpfCnpj": "<cpfCnpj>"
  }
}

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

ParameterTypeRequiredDescription
namestringYesName of the customer, a person or a company.
cpfCnpjstringYesCPF or CNPJ of the customer, digits only.
emailstringNoEmail address where Asaas sends the payment notifications.
mobilePhonestringNoCell phone with area code, digits only, for example 11999998888.
phonestringNoLandline with area code, digits only.
postalCodestringNoCEP of the address, for example 01310-000.
addressstringNoStreet of the address.
addressNumberstringNoNumber of the address.
complementstringNoComplement of the address.
provincestringNoNeighborhood of the address.
companystringNoCompany of the customer.
additionalEmailsstringNoMore email addresses for the payment notifications, separated by commas.
groupNamestringNoName of the group to put the customer in.
externalReferencestringNoIdentifier of the customer in your own system.
observationsstringNoInternal notes about the customer.
notificationDisabledbooleanNotrue 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_create_customer. It becomes your agent's tool definition with no conversion.

Other Asaas tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.