A valid request URL is required to generate request examples{
"capability": {
"available": true,
"reasonCodes": [
"<string>"
],
"message": "<string>"
},
"maintenance": {
"caseId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"phase": "diagnosing",
"reasonCode": "<string>",
"startedAt": "2023-11-07T05:31:56Z",
"lastCheckedAt": "2023-11-07T05:31:56Z",
"expectedCheckAt": "2023-11-07T05:31:56Z",
"impact": "<string>",
"message": "<string>",
"actions": {
"cancel": true,
"recheck": true
}
}
}{
"error": {
"code": "unauthorized",
"reason": "missing_credentials",
"hint": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}404 Not Found{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}Image recovery progress and availability
Requires devices:read and the caller’s permitted device subset. Read the current organization’s owned cloud phone recovery case and availability. Ordinary recovery returns the saved case and cancel/recheck actions; deployments without that runtime retain existing legacy maintenance information. Availability does not change the phone’s main status. Supplier tasks, target images, control credentials and authorization evidence are never exposed.
Hosted deployments only. A local checkout does not mount this route, so calling it there is a 404.
A valid request URL is required to generate request examples{
"capability": {
"available": true,
"reasonCodes": [
"<string>"
],
"message": "<string>"
},
"maintenance": {
"caseId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"phase": "diagnosing",
"reasonCode": "<string>",
"startedAt": "2023-11-07T05:31:56Z",
"lastCheckedAt": "2023-11-07T05:31:56Z",
"expectedCheckAt": "2023-11-07T05:31:56Z",
"impact": "<string>",
"message": "<string>",
"actions": {
"cancel": true,
"recheck": true
}
}
}{
"error": {
"code": "unauthorized",
"reason": "missing_credentials",
"hint": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}404 Not Found{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}Authorizations
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.