Skip to main content
POST
JavaScript
Use este endpoint para mostrar aos clientes exatamente o que será cobrado ao atualizar ou rebaixar sua assinatura, melhorando a transparência e reduzindo solicitações de suporte.

Casos de Uso

  • Confirmação do checkout: Exiba a cobrança proporcional antes que os clientes confirmem uma mudança de plano
  • Calculadoras de preços: Construa calculadoras de upgrade/downgrade em sua aplicação
  • Autoatendimento do cliente: Permita que os clientes explorem opções de plano com preços precisos
  • Validação de desconto: Visualize como os códigos de desconto acumulados afetam o preço de alteração do plano
Você pode incluir discount_codes (um array de até 20 códigos, aplicados em ordem) na solicitação de visualização para ver como os descontos acumulados afetam a cobrança imediata e o novo preço do plano antes de confirmar a alteração. O campo singular discount_code está obsoleto, mas ainda é suportado para compatibilidade retroativa; recomendamos discount_codes daqui para frente.

Campos de Resposta

A resposta de pré-visualização inclui:
O immediate_charge.summary contém o valor total que seria cobrado. Use isso para exibir os preços aos seus clientes antes de confirmarem a mudança de plano.

Autorizações

Authorization
string
header
obrigatório

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

Parâmetros de caminho

subscription_id
string
obrigatório

Subscription Id

Corpo

application/json
product_id
string
obrigatório

Unique identifier of the product to subscribe to

proration_billing_mode
enum<string>
obrigatório

Proration Billing Mode

Opções disponíveis:
prorated_immediately,
full_immediately,
difference_immediately,
do_not_bill,
prorated_immediately_keep_cycle
quantity
integer<int32>
obrigatório

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

Intervalo obrigatório: 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
obsoleto

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
Opções disponíveis:
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.

Opções disponíveis:
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.

Resposta

Preview of subscription plan change

immediate_charge
object
obrigatório
new_plan
object
obrigatório

Response struct representing subscription details

Última modificação em 22 de maio de 2026