A valid request URL is required to generate request examples{
"ok": true,
"service": "<string>",
"status": "ok",
"incident": {
"title": "<string>",
"url": "<string>"
},
"statusPage": "<string>",
"revision": "<string>",
"billing": {
"ok": true,
"viewC": "<string>"
},
"frames": {
"ok": true
},
"webhooks": {
"ok": true
},
"fulfilmentUnwind": {
"ok": true
},
"fleetIntegrity": {
"ok": true
},
"email": {
"ok": true
},
"cloudReadyEmail": {
"enabled": true
},
"liveVideo": {
"state": "configured"
},
"latencyProbes": {
"state": "installed"
},
"opsAlerts": {
"state": "configured",
"reasons": [
"not_hosted"
]
},
"ownerMoney": {
"state": "configured"
},
"staffDirectory": {
"state": "configured"
},
"staffOrgs": {
"state": "configured"
},
"schedules": {
"state": "disabled"
},
"provisioning": {
"state": "disabled"
},
"deviceTakes": {
"state": "disabled"
},
"cloudBillingScan": {
"state": "disabled"
},
"cloudRenewalScan": {
"state": "disabled"
},
"rigTelemetry": {
"ok": true,
"partitionHeadroomMs": 1
},
"opsStream": "listen",
"tenancy": {
"checkout": {
"state": "open",
"mode": "test",
"dayPass": "priced",
"cloudPhone": "priced"
}
}
}Check that the service is up
An unauthenticated liveness probe. status is the one word to branch on: ok, degraded when a background loop has stopped moving, or incident when an operator has declared one. A declared incident also carries incident.title and incident.url.
A hosted deployment running the billing loop reports one boolean for it, and nothing else about the deployment is disclosed.
A valid request URL is required to generate request examples{
"ok": true,
"service": "<string>",
"status": "ok",
"incident": {
"title": "<string>",
"url": "<string>"
},
"statusPage": "<string>",
"revision": "<string>",
"billing": {
"ok": true,
"viewC": "<string>"
},
"frames": {
"ok": true
},
"webhooks": {
"ok": true
},
"fulfilmentUnwind": {
"ok": true
},
"fleetIntegrity": {
"ok": true
},
"email": {
"ok": true
},
"cloudReadyEmail": {
"enabled": true
},
"liveVideo": {
"state": "configured"
},
"latencyProbes": {
"state": "installed"
},
"opsAlerts": {
"state": "configured",
"reasons": [
"not_hosted"
]
},
"ownerMoney": {
"state": "configured"
},
"staffDirectory": {
"state": "configured"
},
"staffOrgs": {
"state": "configured"
},
"schedules": {
"state": "disabled"
},
"provisioning": {
"state": "disabled"
},
"deviceTakes": {
"state": "disabled"
},
"cloudBillingScan": {
"state": "disabled"
},
"cloudRenewalScan": {
"state": "disabled"
},
"rigTelemetry": {
"ok": true,
"partitionHeadroomMs": 1
},
"opsStream": "listen",
"tenancy": {
"checkout": {
"state": "open",
"mode": "test",
"dayPass": "priced",
"cloudPhone": "priced"
}
}
}Response
The service is serving.
Deliberately terse. The backend inventory is reconnaissance material and is never reported on an unauthenticated endpoint.
True whenever the process is serving.
A constant service identifier.
ONE WORD about the whole service, so a reader does not have to invent its own definition of down from the per subsystem booleans below. degraded means at least one of those booleans is false; incident means an operator declared one, and a declaration wins over a clean set of loops because a person can see faults this process cannot. An absent subsystem is a configuration and never counts against this word.
ok, degraded, incident Present only while an operator has declared an incident. A half declaration (a sentence with no link) is discarded rather than published, because a banner whose link goes nowhere teaches people to ignore banners.
Show child attributes
Show child attributes
The public status page, when this deployment has one. Published so a reader links to it without hardcoding an address, and absent rather than guessed when there is none.
The exact build this process is running, as an opaque identifier. Published because it is the only way to tell a deployment that finished from one that is still rolling, and absent when nothing was baked into the image rather than guessed at.
Present only on a hosted deployment that runs the billing loop. viewC appears only while a billing migration is outstanding and names which way it is outstanding.
Show child attributes
Show child attributes
Present only where the frame retention sweep runs.
Show child attributes
Show child attributes
Present only where the webhook delivery loop runs.
Show child attributes
Show child attributes
Present only where the loop that unwinds a paid order that never arrived runs.
Show child attributes
Show child attributes
Whether every device this deployment sells is one the provider still has, and none of them reaches the end of its paid provider term within the alert window (72 hours by default) without being renewed. ABSENT when the verdict is unknown, which is why a reader must treat a missing key as 'not answered' and never as 'fine': staging omits it today and production does not.
Show child attributes
Show child attributes
Whether a notification can reach a person by mail. False is a real and ordinary state: the bell still fills, and nobody is told while the console is shut. Not counted into status.
Show child attributes
Show child attributes
Whether the worker that emails the buyer when a Cloud phone is ready is running in this process. False is the ordinary state until delivery is switched on. Not counted into status.
Show child attributes
Show child attributes
Whether live video for robot-driven phones is switched on here. Never counted into status.
Show child attributes
Show child attributes
Whether the rig latency probe results are available here. Present only on a deployment with a database. Never counted into status.
Show child attributes
Show child attributes
Whether operations alerts reach a person by email here. Never counted into status.
Show child attributes
Show child attributes
Hosted only. A configuration, never counted into status.
Show child attributes
Show child attributes
Hosted only. A configuration, never counted into status.
Show child attributes
Show child attributes
Hosted only. A configuration, never counted into status. A state only, never an organisation id.
Show child attributes
Show child attributes
The customer-facing schedule sweeper. disabled is a configuration and never degrades status.
- Option 1
- Option 2
Show child attributes
Show child attributes
The loop that puts a cloud phone in a customer's hands. disabled means every such order waits for a person, which is why absence is PUBLISHED here rather than left as a missing key.
- Option 1
- Option 2
Show child attributes
Show child attributes
The loop that takes a device back when a session ends without releasing it. disabled means a session that ends badly keeps its machine.
- Option 1
- Option 2
Show child attributes
Show child attributes
The hosted missed-Stripe-webhook Cloud billing scan. disabled means no periodic recovery pass runs on this instance.
- Option 1
- Option 2
Show child attributes
Show child attributes
The hosted managed Cloud term scan. disabled means no periodic pass runs; running can be observation-only, with supplier spending and period-end billing stop separately switched off.
- Option 1
- Option 2
Show child attributes
Show child attributes
Present only on a hosted deployment with a database, where robot arm health samples are kept. Not counted into status.
Show child attributes
Show child attributes
How this replica hears the operator console's live events. listen: a checked database notification channel delivers them as they happen. polling: they are read every 5 seconds, which is also what serves when no notification channel is configured. Present only where the operator surface runs with a database. Never counted into status.
listen, polling Deployment posture, on a hosted deployment only. Enums throughout and never a timestamp, an issuer name or a count: a reader learns which gates are armed, not when one opens.
Show child attributes
Show child attributes