Claim the current guest checkout session into an existing account

Move a guest checkout session — and its held selection — into the caller's existing account instead of creating a new one. Requires both the account's own bearer token (Authorization header) and the guest session token (request body). Repeating the claim with the same account is idempotent; a different account, or a session that is booked or still draft, is rejected.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Body for claiming a guest checkout session into an existing account.

The claiming account's own bearer token travels in the Authorization
header (as on every other authenticated route); the guest session token
travels here in the body because the header already carries the account
credential and both are required together.

string
length ≤ 2048

The guest session token returned by POST /v1/checkout/sessions. A missing, expired, or invalid token is rejected with 401, matching a missing account bearer token.

consents
object
required

Terms and privacy acceptance for this booking. Recorded against the claiming account at claim time — both flags must be true.

Responses

401

Missing, expired, or invalid account bearer token or guest session token

404

Checkout session not found or expired

409

Session already claimed by a different account (CHECKOUT_SESSION_ALREADY_CLAIMED), its status does not admit a claim (CHECKOUT_SESSION_NOT_CLAIMABLE), or a concurrent magic-link exchange briefly holds the claim window — retry shortly (CHECKOUT_SESSION_CLAIM_IN_PROGRESS)

422

Consents missing or not both accepted

503

Database or guest checkout not configured

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json