Create a Subscription Plan
Create a Subscription Plan resource to group and manage recurring payments for individual Subscription resources. You can create a Subscription Plan with or without a trial period.
Headers
Specify the API version of your request. For more details, see Versioning.
The data type being sent in the request body must be application/json.
Request body
The total amount that will be debited in cents (e.g. 100 cents to debit $1.00).
How often the buyer is billed. The possible billing intervals are as follows:
- BIMONTHLY: every 2 months
- BIWEEKLY: every 2 weeks
- BIYEARLY: every 2 years
- DAILY: every day
- MONTHLY: every month
- QUARTERLY: each quarter
- SEMIYEARLY: twice a year
- TRIYEARLY: every 3 years
- WEEKLY: every week
- YEARLY: every year
ISO 4217 3-letter currency code. Currently, the only currency supported is USD.
The total number of billing intervals for subscriptions created from this plan. This is the count of recurring billing cycles, with the interval unit defined by the plan’s billing_interval, such as weekly, monthly, etc. If included, the plan’s duration_type will be set to FIXED_TERM.
Subscriptions created with this plan will use the default duration in the total_billing_intervals field. The subscription's expires_at field will be set to the datetime when the subscription expires based on the plan's default_total_billing_intervals.
A description of the Subscription Plan.
The ID of the Merchant resource that you wish to link to the Subscription Plan (i.e., the merchant that the subscription plan belongs to).
At this time, only approved merchants with one of the following processors are valid:
- DUMMY_V1
- FINIX_V1
The type of the resource that is specified in the linked_to field.
A human-readable name for the resource.
A human-friendly name for the Subscription Plan.
Include up to 50 key: value pairs to annotate requests with custom metadata.
- Maximum character length for individual keys is 40.
- Maximum character length for individual values is 500. (For example, order_number: 25, item_type: produce, department: sales)
Example request
{
"amount": 5000,
"billing_interval": "MONTHLY",
"discount_phase_defaults": {
"amount": 5000
}
}Response
A single Subscription Plan
The ID of the resource.
Timestamp of when the object was created.
Timestamp of when the object was last updated.
ID of the Application the resource was created under.
The ID of the Merchant resource that you wish to link to the Subscription Plan (i.e., the merchant that the subscription plan belongs to).
At this time, only approved merchants with one of the following processors are valid:
- DUMMY_V1
- FINIX_V1
The type of the resource that is specified in the linked_to field.
How often the buyer is billed. The possible billing intervals are as follows:
- BIMONTHLY: every 2 months
- BIWEEKLY: every 2 weeks
- BIYEARLY: every 2 years
- DAILY: every day
- MONTHLY: every month
- QUARTERLY: each quarter
- SEMIYEARLY: twice a year
- TRIYEARLY: every 3 years
- WEEKLY: every week
- YEARLY: every year
A human-readable name for the resource.
A human-friendly name for the Subscription Plan.
A description of the Subscription Plan.
The total amount that will be debited in cents (e.g. 100 cents to debit $1.00).
ISO 4217 3-letter currency code.
The total number of billing intervals for subscriptions created from this plan. This is the count of recurring billing cycles, with the interval unit defined by the plan’s billing_interval, such as weekly, monthly, etc. If included, the plan’s duration_type will be set to FIXED_TERM.
Subscriptions created with this plan will use the default duration in the total_billing_intervals field. The subscription's expires_at field will be set to the datetime when the subscription expires based on the plan's default_total_billing_intervals.
Whether subscriptions created from this plan will have a fixed term or will continue until canceled. If default_total_billing_intervals is set, this plan's duration_type is automatically set to FIXED_TERM. Otherwise, the duration_type is set to EVERGREEN.
Indicates whether the Subscription Plan is usage-based.
The state of the Subscription Plan.
Include up to 50 key: value pairs to annotate requests with custom metadata.
- Maximum character length for individual keys is 40.
- Maximum character length for individual values is 500. (For example, order_number: 25, item_type: produce, department: sales)
Example response
{
"billing_interval": "MONTHLY",
"amount": 5000,
"discount_phase_defaults": {
"amount": 5000
}
}