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

id
string
required

Stable original operation identifier.

Response

Authoritative durable projection.

id
string
required
sourceId
string
required
micros
string
required

Integer micros. One settlement-currency unit equals 1,000,000 micros.

Pattern: ^(0|[1-9][0-9]{0,17})$
currency
string
required
status
enum<string>
required
Available options:
pending,
unknown,
complete,
rejected
customerMessage
string
required
updatedAt
string<date-time>
required
caseId
string