Status

GET /status tells you whether Bazoodle is running normally. It powers Bazoodle’s own status page, needs no sign-in and contains no personal data.

Request

curl -s "https://bazoodle.com/api/v1/status"

Response

{
  "status": "operational",
  "checked_at": 1793051080,
  "components": [
    {"id": "site", "label": "Website", "status": "ok"},
    {"id": "api", "label": "Bazoodle service", "status": "ok"},
    {"id": "signin", "label": "Sign-in", "status": "ok"},
    {"id": "games", "label": "Games and play sessions", "status": "ok"}
  ],
  "maintenance": {"mode": "off", "message": "", "until": ""}
}

Field	Type	Meaning
status	string	The overall state: operational, degraded (a part is down) or maintenance
checked_at	number	When the check ran, in Unix seconds
components	list	One entry per part of Bazoodle; see below
maintenance	object	A notice from the Bazoodle team. mode is off, banner (a heads-up) or full (planned downtime). message is a short text (up to 200 characters) and until an optional time text (up to 60 characters).

A component

Field	Type	Meaning
id	string	A stable code: site (the pages at bazoodle.com), api (the API behind the site), signin (signing in to accounts) or games (starting and joining games).
label	string	The name for people.
status	string	ok (working normally), maintenance (switched off by the Bazoodle team for planned work) or down (a check failed).

New components can be added. Show unknown ones by label and treat any status other than ok as “not working right now”.

Notes

• Cached for 30 seconds, and shared caches may store it. The human version is https://bazoodle.com/status.
• Use it to decide what to show when a request fails: if status is not operational, say that Bazoodle is having trouble instead of blaming your user. Be resilient has a ready-made widget.