Skip to main content

Subscriptions

Subscriptions combine a customer, a plan and a payment method into an operational recurring billing cycle.

Public routes

  • POST /v1/subscriptions
  • GET /v1/subscriptions
  • GET /v1/subscriptions/{id}
  • PATCH /v1/subscriptions/{id}
  • POST /v1/subscriptions/{id}/pause
  • POST /v1/subscriptions/{id}/resume
  • POST /v1/subscriptions/{id}/cancel
  • POST /v1/subscriptions/{id}/reactivate
  • POST /v1/subscriptions/{id}/change-plan
  • POST /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.