Retrieve a checkout session
Authentication
AuthorizationBearer
A secret key (rl_sk_test_..., rl_sk_live_...) or a restricted key with limited scopes (rl_rk_test_..., rl_rk_live_...). A restricted key can carry agent: true and an expires_at, and is what a coding agent should hold. Keys end in a checksum so secret scanners can recognize them. People create, roll and revoke keys in the dashboard; GET /v1/api_keys lists them, masked.
Path parameters
checkout_session_id
The checkout session ID (cs_...).
Response
The checkout session.
id
object
customer
mode
top_up buys credits, subscription starts a plan, payment_method saves a card for postpaid invoices.
Allowed values:
status
Allowed values:
url
The hosted page to send the customer to.
expires_at
payment_provider
The name of the provider hosting the page, chosen by routing unless the request named one.
livemode
created_at
success_url
cancel_url
credits
plan
amount_total
An amount of money in the currency's minor unit.
result
What completion produced.
provider_reference
The provider's ID for the payment, for reconciliation.
payment
The provider-neutral payment record (pay_...), once the customer has paid.
metadata
Up to 50 keys of your own, with keys up to 40 characters and values up to 500 characters.
completed_at
Errors
400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
404
Not Found Error
429
Too Many Requests Error
500
Internal Server Error