Skip to main content
POST
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

deviceId
string
required

The owned cloud phone's deviceId.

Body

application/json

Only the observed video symptom.

observation
object
required

Response

Observation acknowledged. Consult accepted, caseId and reason; acknowledgement is not recovered video.

accepted
boolean

Whether a device recovery case was recorded. HTTP 202 alone does not establish device recovery.

caseId
string<uuid>

The original saved case, if accepted.

reason
string

Why no case was recorded, when present. Client connection faults are local_connection; unconfirmed service is service_unconfirmed.