List checkouts
Cursor-paginated summaries, newest first. Deliberately a summary rather than the full object: the full shape carries the whole event timeline, which is exactly what a list view must not fetch.
Requires the checkouts.read scope.
?subject= narrows the page to one end user, and each row carries subject when the checkout has one. A subject-bound key is already narrowed to its own end user; asking for another’s is a 403.
Authorizations
Authorization: Bearer ck_test_… or ck_live_…. There is no other auth scheme — no query-string keys, no request signing, no OAuth.
Query Parameters
Page size. Must be an integer from 1 to 100; anything else is a 400.
1 <= x <= 100The previous page's nextCursor — an ISO 8601 timestamp. Returns rows created strictly before it.
Filter to one status. An unrecognised value is a 400, not an empty page.
succeeded, failed and cancelled are terminal; nothing leaves them.
queued, running, awaiting_user_action, succeeded, failed, cancelled Filter to one end user. Composes with status, limit and cursor; a subject with no checkouts is an empty page, not an error.
A subject-bound key does not need this — its page is already narrowed to one person. Passing its own subject is fine; naming a different one is a 403, refused rather than quietly ignored.
Validated like every other subject: 1 to 200 characters, or 400.
1 - 200