Skip to main content
POST
JavaScript
Verwenden Sie diesen Endpunkt, um den Kunden genau zu zeigen, was ihnen bei einem Upgrade oder Downgrade ihres Abonnements berechnet wird, wodurch die Transparenz verbessert und Supportanfragen reduziert werden.

Anwendungsfälle

  • Checkout-Bestätigung: Zeigen Sie die anteilige Gebühr an, bevor Kunden eine Planänderung bestätigen
  • Preisrechner: Erstellen Sie Upgrade-/Downgrade-Rechner in Ihrer Anwendung
  • Kunden-Selbstbedienung: Ermöglichen Sie es Kunden, Tarifoptionen mit genauen Preisen zu erkunden
  • Rabattvalidierung: Zeigen Sie an, wie gestapelte Rabattcodes die Preisgestaltung bei der Planänderung beeinflussen
Sie können discount_codes (ein Array von bis zu 20 Codes, in der Reihenfolge angewendet) in der Vorschauanforderung einfügen, um zu sehen, wie die gestapelten Rabatte die sofortige Gebühr und die neue Tarifpreisgestaltung beeinflussen, bevor Sie die Änderung vornehmen. Das einzelne discount_code Feld ist veraltet, wird aber aus Gründen der Abwärtskompatibilität weiterhin unterstützt; wir empfehlen discount_codes für die Zukunft.

Antwortfelder

Die Vorschau-Antwort enthält:
Der immediate_charge.summary enthält den Gesamtbetrag, der berechnet werden würde. Verwenden Sie dies, um Ihren Kunden die Preise anzuzeigen, bevor sie die Planänderung bestätigen.

Autorisierungen

Authorization
string
header
erforderlich

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Pfadparameter

subscription_id
string
erforderlich

Subscription Id

Body

application/json
product_id
string
erforderlich

Unique identifier of the product to subscribe to

proration_billing_mode
enum<string>
erforderlich

Proration Billing Mode

Verfügbare Optionen:
prorated_immediately,
full_immediately,
difference_immediately,
do_not_bill,
prorated_immediately_keep_cycle
quantity
integer<int32>
erforderlich

Number of units to subscribe for. Must be at least 1.

Erforderlicher Bereich: x >= 0
adaptive_currency_fees_inclusive
boolean | null

Whether adaptive currency fees should be included in the price (true) or added on top (false). If not specified, uses the subscription's stored setting.

addons
Attach Addon Request · object[] | null

Addons for the new plan. Note : Leaving this empty would remove any existing addons

Cancel the payment link of a pending plan change, so that this change can replace it.

The link is cancelled only if the customer has not started to pay. A paid or in-progress payment gives a 409. A failed cancel gives a 503, and a retry is safe.

The request is validated before the cancel. A later failure, for example an amount below the minimum, leaves the subscription on its current plan with no open link. A retry is safe.

The preview route shares this request body and ignores this field.

cancel_scheduled_change_plan
boolean

Replace a scheduled plan change with this one.

The scheduled change is cancelled by the transaction that applies this change. A change that never applies leaves the schedule in place.

effective_at: next_billing_date is allowed. The new schedule then replaces the old one in the request transaction.

A pending plan change still gets a 409. This field does not affect it.

The preview route shares this request body, so a preview that sets this field also passes the scheduled-change 409.

Collect the plan-change amount with a payment link. The customer then pays on a checkout page.

The business needs the allow_plan_change_via_payment_link capability. The request needs effective_at: immediately. The request also needs on_payment_failure: prevent_change.

The preview route shares this request body and ignores this field.

discount_code
string | null
veraltet

DEPRECATED: Use discount_codes instead. Cannot be used together with discount_codes.

discount_codes
string[] | null

Stacked discount codes to apply to the new plan. Max 20. Cannot be used together with discount_code. If provided, replaces any existing discount codes. Empty array removes all discounts. If not provided (None), existing discounts with preserve_on_plan_change=true are preserved.

effective_at
enum<string>

When to apply the plan change.

  • immediately (default): Apply the plan change right away
  • next_billing_date: Schedule the change for the next billing date
Verfügbare Optionen:
immediately,
next_billing_date
metadata
null | Metadata · object

Metadata for the payment. If not passed, the metadata of the subscription will be taken

on_payment_failure
null | enum<string>

Controls behavior when the plan change payment fails.

  • prevent_change: Keep subscription on current plan until payment succeeds
  • apply_change (default): Apply plan change immediately regardless of payment outcome

With effective_at: next_billing_date, the plan change payment replaces the renewal payment. If that payment fails with prevent_change, the plan change is cancelled. The subscription then renews on the current plan, with the usual payment retries.

If not specified, uses the business-level default setting.

Verfügbare Optionen:
prevent_change,
apply_change
return_url
string | null

The URL that receives the customer after they pay the payment link. Needs collect_via_payment_link: true. Without it, the request gets a 422. A change that collects no money issues no link and does not use the URL. The preview route validates this field but does not use it.

The redirect adds subscription_id, payment_id and status. The status value is the status of the plan-change payment. It is not the status of the subscription. When that payment fails, the subscription stays active on its current plan. To try again, call this endpoint again to get a new link. The new plan can apply after the redirect, when the payment webhook arrives.

Antwort

Preview of subscription plan change

immediate_charge
object
erforderlich
new_plan
object
erforderlich

Response struct representing subscription details

Zuletzt geändert am 22. Mai 2026