/v1/status
Whether BlueBot itself is up. Needs no key. For your own Mac, see GET /v1/device.
Needs no key.
Example
/v1/statuscurl "https://usebluebot.com/api/v1/status" \
-H "Authorization: Bearer $BLUEBOT_API_KEY"Response
200: BlueBot’s status.
object"status"requiredstatusstringrequiredok;degradedwhen BlueBot stopped sending for everyone;downwhen it can’t reach its database.One of
ok,degraded,down.sendingstringrequiredok;stoppedwhile BlueBot has stopped all sending, during an incident;unknownwhen BlueBot can’t reach its database to check. Macs can’t pick up texts while the database is down, so queued texts wait.One of
ok,stopped,unknown.databasestringrequiredOne of
ok,down.api_versionstringrequiredchecked_attimestamprequiredWhen this was checked.
Response200
{
"object": "status",
"status": "ok",
"sending": "ok",
"database": "ok",
"api_version": "2026-11-13",
"checked_at": "2026-11-13T19:41:00.000Z"
}Errors
Every refusal has the same envelope and a page of its own. These are the ones this operation can give.
| Code | Status | What it means |
|---|---|---|
| 429 | Too many requests. A key may make 120 requests a minute. The RateLimit header says how many are left, and Retry-After how long to wait. | |
| 500 | Something went wrong on BlueBot’s side. It was reported. Send the request again; with an Idempotency-Key that is always safe. | |
| 503 | BlueBot isn’t taking requests right now, during maintenance or an incident. GET /v1/status says what is going on. |
Try it
Call this operation from the page with your own key. The key stays in this tab and is forgotten when you leave.