Finance and payments
Asaas in your product and your AI agents, through one API
The Asaas toolkit covers customers, payments (cobrancas) and subscriptions: list, read, create and update them, and delete payments. Connect stores the API key of each customer, logs every execution and exposes each operation as a JSON Schema tool, so your product or AI agent bills through Asaas without building the integration.
15 days to try it. No credit card.
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>"
}
}How it works
From a connected customer to the first Asaas call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Asaas account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Asaas.
Bill from inside your SaaS
Create a customer and a payment by boleto, Pix or credit card, then send the invoiceUrl returned by Create payment to the payer.
Recurring plans on Asaas
Create a subscription for a customer and let Asaas generate one payment per cycle; read those payments with List payments filtered by subscription.
Billing agent for finance teams
An AI agent lists overdue payments, reads each one and updates the due date or removes a payment, all logged in the Connect audit trail.
Tools
12 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.
- Update customerPUTUpdates a customer. Fields not sent stay as they are.
- 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.
- List subscriptionsGETLists the subscriptions, optionally filtered by customer, status, billing type or external reference. The payments a subscription generates come from List payments with the subscription filter. Page with offset and limit while hasMore is true.
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.
Questions about the Asaas toolkit
Do I need to build against the Asaas API?
No. Connect ships 12 Asaas tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Asaas account?
With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
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