A Subscription object represents an ongoing billing relationship where a customer is charged on a recurring basis. Subscriptions are created when a customer purchases a subscription Product and manage the lifecycle of recurring Payments. Subscriptions track billing intervals, status changes, and link to all associated Payments and Orders. You can use the API to manage subscriptions including updating, pausing, and cancelling them.Documentation Index
Fetch the complete documentation index at: https://docs.fungies.io/llms.txt
Use this file to discover all available pages before exploring further.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
GET | /v0/subscriptions/list | List and filter subscriptions |
POST | /v0/subscriptions/create | Create a new subscription |
GET | /v0/subscriptions/{subscriptionIdOrNumber} | Retrieve a subscription |
PATCH | /v0/subscriptions/{subscriptionIdOrNumber}/update | Update a subscription |
POST | /v0/subscriptions/{subscriptionIdOrNumber}/charge | Charge a subscription immediately |
PATCH | /v0/subscriptions/{subscriptionIdOrNumber}/cancel | Cancel a subscription |
PATCH | /v0/subscriptions/{subscriptionIdOrNumber}/pause-collection | Pause subscription billing |
The Subscription object
Object type identifier. Always
"subscription" for Subscription objects.Subscription identifier, based on the initial order number.
Current subscription status. Possible values:
active, past_due, canceled, unpaid, incomplete, incomplete_expired, trialing, pausedUnix timestamp (milliseconds) when the subscription was created.
Unix timestamp (milliseconds) when the current billing interval started.
Unix timestamp (milliseconds) when the current billing interval ends.
Whether the subscription will cancel at the end of the current interval. Defaults to
false.Unix timestamp (milliseconds) when the subscription was cancelled, if applicable.
Expanded User object with basic subscriber information.
Human-readable number of the initial order.
Expanded Order object for the initial subscription order.
Human-readable number of the most recent payment.
Expanded Payment object for the most recent charge.
Subscription lifecycle
Example response
Webhook events
| Event | Typical use |
|---|---|
subscription_created | Subscription exists; first payment may still be processing |
payment_success | First or recurring charge succeeded — fulfill here |
subscription_interval | New billing period charged (renewal) |
subscription_updated | Plan change, cancel-at-period-end, trial ended, etc. |
subscription_cancelled | Subscription ended |
subscription_created can include PENDING payments and why you should not rely on it alone for access grants.
Related resources
Payments
Payment transactions for subscriptions
Orders
Initial orders creating subscriptions
Users
Subscribed customers
Events
Subscription webhook events