Subscriptions
Subscriptions combine a customer, a plan and a payment method into an operational recurring billing cycle.
Public routes
POST /v1/subscriptionsGET /v1/subscriptionsGET /v1/subscriptions/{id}PATCH /v1/subscriptions/{id}POST /v1/subscriptions/{id}/pausePOST /v1/subscriptions/{id}/resumePOST /v1/subscriptions/{id}/cancelPOST /v1/subscriptions/{id}/reactivatePOST /v1/subscriptions/{id}/change-planPOST /v1/subscriptions/{id}/update-card
Recommendations
- Persist
subscription_id, current period and next billing date. - Do not treat webhooks as email-only notifications; they are part of the financial close.
- Keep immediate cancellation separate from end-of-period cancellation in your domain model.
Did this page unblock the next step?
Feedback stays inside the docs flow and should never include customer or card data.