Sign in
Subscriptions API

Create subscription

With subscriptions, you can schedule recurring payments to take place at regular intervals.

For example, by simply specifying an amount and an interval, you can create an endless subscription to charge a monthly fee, until you cancel the subscription.

Or, you could use the times parameter to only charge a limited number of times, for example to split a big transaction in multiple parts.

A few example usages:

amount[currency]="EUR" amount[value]="5.00" interval="2 weeks" Your customer will be charged €5 once every two weeks.

amount[currency]="EUR" amount[value]="20.00" interval="1 day" times=5 Your customer will be charged €20 every day, for five consecutive days.

amount[currency]="EUR" amount[value]="10.00" interval="1 month" startDate="2018-04-30" Your customer will be charged €10 on the last day of each month, starting in April 2018.

post/v2/customers/{customerId}/subscriptions

Headers

idempotency-keystring
Example:123e4567-e89b-12d3-a456-426

A unique key to ensure idempotent requests. This key should be a UUID v4 string.

Request body

resourcestring

Indicates the response contains a subscription object. Will always contain the string subscription for this endpoint.

idstring
mode'live' | 'test'

Whether this entity was created in live mode or in test mode.

status'pending' | 'active' | 'canceled' | 'suspended' | 'completed'

The subscription's current status is directly related to the status of the underlying customer or mandate that is enabling the subscription.

timesinteger nullable

Total number of payments for the subscription. Once this number of payments is reached, the subscription is considered completed.

Test mode subscriptions will get canceled automatically after 10 payments.

timesRemaininginteger nullable

Number of payments left for the subscription.

intervalstring

Interval to wait between payments, for example 1 month or 14 days.

The maximum interval is one year (12 months, 52 weeks, or 365 days).

Possible values: ... days, ... weeks, ... months.

startDatestring

The start date of the subscription in YYYY-MM-DD format.

nextPaymentDatestring nullable

The date of the next scheduled payment in YYYY-MM-DD format. If the subscription has been completed or canceled, this parameter will not be returned.

descriptionstring

The subscription's description will be used as the description of the resulting individual payments and so showing up on the bank statement of the consumer.

Please note: the description needs to be unique for the Customer in case it has multiple active subscriptions.

method'creditcard' | 'directdebit' | 'paypal' | 'null' nullable

The payment method used for this subscription. If omitted, any of the customer's valid mandates may be used.

webhookUrlstring nullable

We will call this URL for any payment status changes of payments resulting from this subscription.

This webhook will receive all events for the subscription's payments. This may include payment failures as well. Be sure to verify the payment's subscription ID and its status.

customerIdstring
mandateIdstring
createdAtstring

The entity's date and time of creation, in ISO 8601 format.

canceledAtstring nullable

The subscription's date and time of cancellation, in ISO 8601 format. This parameter is omitted if the subscription is not canceled (yet).

profileIdstring

The identifier referring to the profile this entity belongs to.

Most API credentials are linked to a single profile. In these cases the profileId can be omitted in the creation request. For organization-level credentials such as OAuth access tokens however, the profileId parameter is required.

testmodeboolean nullable

Whether to create the entity in test mode or live mode.

Most API credentials are specifically created for either live mode or test mode, in which case this parameter must not be sent. For organization-level credentials such as OAuth access tokens, you can enable test mode by setting testmode to true.

Example request

{
  "resource": "subscription",
  "id": "sub_5B8cwPMGnU",
  "mode": "live",
  "status": "active",
  "amount": {
    "currency": "EUR",
    "value": "10.00"
  },
  "times": 6,
  "timesRemaining": 5,
  "interval": "2 days",
  "startDate": "2025-01-01",
  "nextPaymentDate": "2025-01-01",
  "description": "Subscription of streaming channel",
  "method": "paypal",
  "applicationFee": {
    "amount": {
      "currency": "EUR",
      "value": "10.00"
    },
    "description": "Platform fee"
  },
  "webhookUrl": "https://example.com/webhook",
  "customerId": "cst_5B8cwPMGnU",
  "mandateId": "mdt_5B8cwPMGnU",
  "createdAt": "2024-03-20T09:13:37+00:00",
  "canceledAt": "2025-01-01T13:10:19+00:00",
  "profileId": "pfl_5B8cwPMGnU",
  "_links": {
    "self": {
      "href": "https://...",
      "type": "application/hal+json"
    },
    "customer": {
      "href": "https://...",
      "type": "application/hal+json"
    },
    "mandate": {
      "href": "https://...",
      "type": "application/hal+json"
    },
    "profile": {
      "href": "https://...",
      "type": "application/hal+json"
    },
    "payments": {
      "href": "https://...",
      "type": "application/hal+json"
    },
    "documentation": {
      "href": "https://...",
      "type": "application/hal+json"
    }
  }
}

Response

The newly created subscription object.

Changes

Changed in 4 of the 78 revisions of this API.617

  • 00fb770ca93410See the full diff
    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

    • ○

      the response property //// became required for the status

      response-property-became-required

  • 327472893a8964See the full diff
    • ▲

      the request property / became not nullable

      request-property-became-not-nullable

    • ▲

      the request property / became not nullable

      request-property-became-not-nullable

    • ▲

      the request property // became required

      request-property-became-required

    • ▲

      the request property // became required

      request-property-became-required

    • ▲

      the request property // became required

      request-property-became-required

    • ▲

      the request property // became required

      request-property-became-required

    • ○

      the response property ////// became required for the status

      response-property-became-required

    • ○

      the response property ////// became required for the status

      response-property-became-required

    • ○

      the response property ////// became required for the status

      response-property-became-required

    • ○

      the response property ////// became required for the status

      response-property-became-required

  • 7cab62b218301See the full diff
    • ○

      added the non-success response with the status

      response-non-success-status-added

  • ef4b5a97b56a2See the full diff
    • ○

      the endpoint scheme security advancedAccessToken was added to the API

      api-security-added

    • ○

      the endpoint scheme security organizationAccessToken was removed from the API

      api-security-removed

    This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 78 revisions, 9 have no diff computed.