Platform status
Read live component health, 90-day history, and uptime from GET /v1/status — or the human status page at hannu.africa/status.
Platform health is available two ways: a machine-readable endpoint for your systems, and a human page for a quick look.
Read status from the API
GET /v1/status returns the current health of each platform component, a 90-day history, and uptime. Poll it from monitoring, or surface it in your own status view.
curl https://api.hannu.africa/v1/status \
-H "Authorization: Bearer $HANNU_KEY"The response is returned directly, with no { data } envelope. It carries the overall status, a components array, and a history map and an uptime map keyed by component key — enough to drive an alert or render a dashboard.
{
"status": "operational",
"summary": "All systems operational",
"updated_at": "2026-07-17T12:00:00Z",
"components": [
{ "key": "api", "name": "Platform API", "group": "Platform", "status": "operational", "description": "Task creation, tracking and the MCP server." },
{ "key": "payouts", "name": "Operator payouts", "group": "Money", "status": "operational", "description": "Batching and sending Operator payouts in naira." }
],
"history": {
"api": [{ "day": "2026-07-16", "status": "operational" }]
},
"uptime": {
"api": 0.9998,
"payouts": 0.9997
}
}The component list and values above are illustrative — read the live endpoint for the current picture. A component's status is one of operational, degraded, partial_outage, or major_outage, and uptime is reported as a fraction of operational days over the trailing 90 days.
The human status page
For a quick visual check — component states, incident history, and the 90-day timeline — use the web page at hannu.africa/status. It reads from the same source as the API.
Point monitoring at GET /v1/status rather than scraping the web page. The endpoint is the machine-readable contract; the web page is for people.