This endpoint is responsible for removing an existing subscription, terminating its recurrence and preventing the generation of new payments.
In addition to removing the subscription, Asaas also removes pending or overdue payments that still belong to that recurrence, preventing new payment requests from being sent to the payer.
When to use
Use this endpoint when your integration needs to:
- permanently cancel a subscription;
- terminate a recurrence requested by the customer;
- stop the automatic generation of new payments;
- remove a subscription that was created incorrectly;
- replace a subscription with another one using new settings.
If your intention is to temporarily pause the recurrence, we recommend using the Update Subscription endpoint and changing the status to INACTIVE.
Important parameter
This endpoint uses only one required parameter:
- id — the unique identifier of the subscription in Asaas.
This identifier is returned when the subscription is created and should be stored by your application.
Important business rules
When removing a subscription:
- new payments will no longer be generated;
- pending or overdue payments belonging to the subscription are removed;
- payments that have already been paid remain recorded to preserve the financial history;
- the subscription is no longer part of the recurring flows in the integration.
The removal affects only the specified subscription.
How it works
Simplified flow:
Active subscription
↓
Removal request
↓
Subscription removed
↓
Pending or overdue payments removed
↓
No new payments will be generatedImportant behaviors
After removal:
- the subscription will no longer be able to generate new payments;
- future payments will no longer exist;
- payments that have already been settled remain available for consultation;
- Webhooks related to existing payments may continue to be received if events were generated before the removal.
ImportantRemoving a subscription is different from suspending it.
Suspension (
INACTIVE) temporarily stops the generation of payments, while removal permanently terminates the recurrence.
Best practices
Recommended
- Confirm the user's intent before removing a subscription.
- Internally store the reason for the cancellation for auditing purposes.
- Use Webhooks to keep your system synchronized after the removal.
- If there is a possibility of resuming the recurrence, prefer suspending the subscription instead of removing it.
Common errors
400 Bad Request
400 Bad RequestThis may occur when the provided identifier has an invalid format.
401 Unauthorized
401 UnauthorizedOccurs when the API Key is invalid or belongs to a different environment.
404 Not Found
404 Not FoundOccurs when the specified subscription does not exist or does not belong to the authenticated account.
Operational impacts
Removing a subscription permanently stops the recurring payment generation cycle.
If your application has billing processes, financial reconciliation, automatic notifications, or integrations with external systems, it is recommended to immediately update the internal status of the subscription to avoid new payment attempts or inconsistencies between systems.
Related content
- Create subscription
- Update subscription
- Retrieve a single subscription
- List subscriptions
- List subscription payments
- Subscription Webhooks
404Not found
