Vorschau auf Planänderung
Vorschau auf die Auswirkungen einer Änderung des Abonnementplans, bevor Sie sich dafür entscheiden. Gibt den sofort fälligen Betrag und die neuen Abonnementdetails zurück, ohne tatsächliche Änderungen vorzunehmen.
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
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:Autorisierungen
Send your API key as a bearer token: Authorization: Bearer <api_key>. A test mode key starts with dodo_test_, for example dodo_test_AbCd1234EfGh5678.<secret>. A live mode key starts with dodo_live_. Use a test mode key on test.dodopayments.com and a live mode key on live.dodopayments.com. Keys from before these tags have no tag and operate as before.
Body
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.
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.
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.
Controls behavior when the plan change payment fails.
prevent_change: Keep subscription on current plan until payment succeedsapply_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.
prevent_change, apply_change 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.