API reference, Console billing
Open the Stripe Customer Portal
POST/v1/console/billing-portal-sessionsoperation id createBillingPortalSession
Creates a Stripe Customer Portal session for the account's Stripe customer: invoices, payment method, cancel
or switch plans. Send the browser to url; Stripe returns it to return_path. Answers 409
no_subscription for an account without a Stripe customer (it never bought anything), and 503 maintenance
while the portal is not configured for Dex (Subscription.billing_portal is false then).
Authentication. Console session cookie (__Host-dex_session), or an app session token (Authorization: Bearer dex_ses_...). With the cookie, state-changing routes also need the x-dex-csrf header.
Parameters
x-dex-csrfheader ยท stringcsrf_token returned by createSession (or handed over in the completeGoogleSignIn redirect). Required
with the session cookie on every state-changing console route; not used with a bearer app session.32 to 64 characters
Request body
application/json, schema BillingPortalSessionRequest
return_pathstringpattern ^/[A-Za-z0-9/_-]{0,200}$
Responses
201Portal session created; send the browser to url.
Headers: x-request-id
objectstringrequiredalways "billing_portal_session"
urlstringrequiredformat uri
400The request could not be read. Codes: invalid_json (not JSON, not UTF-8, or a \u escape that is half of a
surrogate pair, such as "\ud800" without its low half), duplicate_key (a JSON object
repeats a key; param is the JSON pointer of the repeated member, such as /questions/q1/options/a),
unsupported_media_type (not application/json) and invalid_header (a malformed idempotency-key or
x-client-request-id; param names the header).
Headers: x-request-id, x-client-request-id
Error envelope. See Errors for every type and code.
401Missing, unknown, revoked or expired credentials.
Headers: x-request-id, x-client-request-id
Error envelope. See Errors for every type and code.
403The credentials are valid but not allowed to do this (missing scope, suspended account or failed CSRF check).
Headers: x-request-id, x-client-request-id
Error envelope. See Errors for every type and code.
409The idempotency key was used with a different body, or the first request with this key is still running.
Console billing routes also answer 409 for a state conflict: subscription_exists (createSubscriptionCheckout
while a subscription is live, joinWaitingList for a plan the account holds), no_subscription
(updateSubscription, cancelSubscription, createResetCheckout or createBillingPortalSession without one),
plan_sold_out (createSubscriptionCheckout or updateSubscription to a plan with no founding-round seat left;
with hints), key_revoked (updateKey on a revoked key).
Headers: x-request-id, x-client-request-id, retry-after
Error envelope. See Errors for every type and code.
422The request is well-formed JSON but breaks a validation rule. param names the field as a dotted path.
Codes: unknown_field, missing_field, invalid_type (wrong JSON type), invalid_value (right type, value
out of range: an empty or over-long string, a state, instructions, criteria string or option description
of only whitespace, an empty questions or options object, an empty state object or array, a pattern or
allowed-value mismatch such as a label or level with outer whitespace, a state nested deeper than 32 levels, a
bad date or date range), field_not_allowed (options or levels on the wrong question type),
invalid_question_id, too_many_questions, too_many_options, invalid_levels (including two levels equal
after Unicode NFC normalisation and lower-casing), invalid_min_confidence, duplicate_label (two option
labels equal after Unicode NFC normalisation and lower-casing, such as Billing and billing),
state_path_not_found, state_not_json and, on the console, top_up_limit_exceeded.
Headers: x-request-id, x-client-request-id
Error envelope. See Errors for every type and code.
500An unexpected error. Any charge was refunded. Retry with the same idempotency key.
Headers: x-request-id, x-client-request-id
Error envelope. See Errors for every type and code.
503maintenance: the console's database, sign-in or payments are unavailable for a moment (for
createGoogleSession also: Google sign-in is not configured, or Google's signing keys cannot be fetched).
Retry after retry-after. Nothing was changed.
Headers: x-request-id, retry-after
Error envelope. See Errors for every type and code.
Examples
Illustrative values. Examples show the shape of requests and responses; the numbers in them are not measured results.
Request: portal
{
"return_path": "/console/billing"
}Response: portal
{
"object": "billing_portal_session",
"url": "https://billing.stripe.com/p/session/live_YWNjdF8xTz"
}