Expire a checkout session
Manually expire an open checkout session. Only sessions with status 'open' or 'pending' and no active payment attempt can be expired.
/checkout-sessions/{id}/expireManually expire an open checkout session. Only sessions with status 'open' or 'pending' and no active payment attempt can be expired.
Related endpoints
POST /checkout-sessions— Create a checkout sessionGET /checkout-sessions/{id}— Retrieve a checkout session
Common errors
401 authentication_error— missing, invalid, expired, or revoked credential. Codes:authentication_failed,invalid_api_key,expired_api_key,api_key_revoked,session_invalid,merchant_required. Carries aWWW-Authenticate: Bearerchallenge.404 resource_missing— the referenced resource does not exist or is not visible to your key.409 conflict— Idempotency-Key collision with a different body, or a concurrent state-transition conflict.
Idempotency
Pass an Idempotency-Key header (UUID v4 recommended) to make retries safe. Keys are valid for 24 hours; see the idempotency guide.
Your RevKeen merchant API key. Create and manage keys in Dashboard → Settings → Developer. Use rk_sandbox_* for staging/test and rk_live_* for production. The same key may be sent as Authorization: Bearer <key> if that suits your HTTP client better. A missing, invalid, expired, or revoked key returns 401 with a WWW-Authenticate: Bearer challenge; a valid key without the required scope returns 403.
In: header
Path Parameters
Checkout session ID to expire.
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://api.revkeen.com/v2/checkout-sessions/11111111-1111-4111-8111-111111111111/expire" \
-H "x-api-key: $REVKEEN_API_KEY"Synthetic documentation data, validated against the response schema; not a live API result.
{ "data": { "id": "00000000-0000-4000-8000-000000000001", "status": "expired", "expired_at": "2026-09-01T12:00:00Z" }, "requestId": "00000000-0000-4000-8000-000000000001"}