Skip to main content
GET
Error

Authorizations

Authorization
string
header
required

The control surface credential. Send Authorization: Bearer <token>.

Two kinds of token are accepted and they are told apart by shape, not by a separate header. A token beginning pbk_ or puk_ is an org scoped API key, whose public half and secret half are generated together and of which only a hash of the secret is ever stored; anything else is treated as an OAuth 2.1 access token and verified against the authorization server's keys.

Both resolve to the same context: an org, a principal and a set of scopes. Nothing downstream branches on which channel you used, with one deliberate exception, key management, which requires a signed-in person so that a key can never mint another key.

Scopes are enforced when MCP tools are REGISTERED rather than when they are called, so a tool your credential cannot use is absent from tools/list rather than refused mid gesture.

Path Parameters

orderId
string
required

The order id, as POST /v1/checkout-sessions returned it.

Response

This checkout's payment status.

Where one checkout's payment got to. Phones and their delivery are listed by GET /v1/fulfilments.

orderId
string
required

The order id, as POST /v1/checkout-sessions returned it.

payment
enum<string>
required

pending: no payment recorded yet, including a delayed payment method that is still clearing. paid: the payment was recorded. failed: the payment did not go through. closed: the checkout ended without a payment (it expired, a newer checkout replaced it, or it could not be opened).

Available options:
pending,
paid,
failed,
closed