Sozuri Developer Documentation

Live status of the Sozuri platform and its connections to Safaricom, Airtel and Telkom, read from the status endpoint every time this page loads, plus a record of recent incidents. Bookmark this page when you’re running a high-volume campaign or just want to confirm the platform is healthy.

Programmatic status endpoint
Sozuri services
Carrier connectivity
Incidents

Programmatic status endpoint

Probe the platform programmatically before scheduled high-volume runs or from external uptime monitors. No authentication is required, and the probe sends nothing to any network.

GET https://sozuri.net/api/v1/status

Live response

Loading current status…

Example response

{
  "status": "operational",
  "carriers": {
    "safaricom": "operational",
    "airtel": "operational",
    "telkom": "operational"
  },
  "components": {
    "database": "operational",
    "cache": "operational"
  },
  "version": "1.0",
  "timestamp": "2026-05-14T12:34:56+03:00"
}

Field reference

Field	Type	Meaning
`status`	string	Overall status: `down` when the database or the cache is down; otherwise `degraded` when any carrier is not `operational`; otherwise `operational`.
`carriers.safaricom`	string	`operational`, `degraded` or `unknown`. `degraded` means Sozuri cannot currently sign in to Safaricom to submit messages; `unknown` means the check itself could not run.
`carriers.airtel`, `carriers.telkom`	string	`operational` or `degraded`. `degraded` means Sozuri’s route to that carrier is not set up, so nothing can be submitted to it.
`components.database`	string	`operational` or `down`: whether Sozuri can reach its database.
`components.cache`	string	`operational` or `down`: whether Sozuri can reach its cache and queue layer.
`version`	string	Application version string, currently `1.0`.
`timestamp`	string	ISO-8601 time of the probe, in East Africa Time (`+03:00`).

The carrier values describe whether Sozuri can submit to each network right now. They do not measure delivery rates, and a carrier can be operational here during a problem on the carrier’s own side.

Status values

Value	Meaning	Recommended action
operational	Healthy.	Proceed.
degraded	For a carrier: Sozuri cannot currently submit to it. Overall: at least one carrier is degraded or unknown.	Check `carriers`. Messages to the other carriers can go ahead; defer sends to the affected one.
down	The database or the cache cannot be reached (only `status` and `components` use this value).	Do not start a scheduled run; wait and re-probe.
unknown	The Safaricom check could not run (only `carriers.safaricom` uses this value).	Treat as degraded.

HTTP semantics:

200 — overall status is operational or degraded; submissions can be attempted.
503 — overall status is down: the database or the cache is unreachable. The body has the same fields. Defer the scheduled run.

Polling guidance: Probe once a few minutes before a known burst; for continuous uptime checks, poll no more frequently than once every 30 seconds.

Example (curl)

curl -sS https://sozuri.net/api/v1/status | jq

Sozuri services

The SMS and carrier rows below are filled from the live endpoint when this page loads. Services that the endpoint does not report on are not listed here; if you suspect a problem with one of them, contact [email protected].

Platform

Service	Status
SMS API	…
Airtime	UNAVAILABLE

Carrier connectivity

Carrier	Status
Safaricom	…
Airtel	…
Telkom	…

Incidents

Recent and ongoing incidents. Click any entry to expand for details.

Ongoing Airtime service unavailable Ongoing

The Airtime top-up service (/api/v1/airtime/topup) is currently unavailable while we work with upstream providers to restore service. No timeline for resumption has been confirmed. SMS, WhatsApp and Premium SMS are not affected.

If your application depends on airtime top-up, contact [email protected] for an update or to discuss alternatives.

Resolved SMS submission errors on /api/v1/messaging 15 May 2026

On 15 May 2026 a subset of submissions to POST /api/v1/messaging returned a malformed response body (the client received only {"message": "Server Error"}) instead of the expected JSON envelope. The issue surfaced during an upstream routing transition affecting a portion of bulk SMS traffic. Service was restored the same day and the underlying failure mode is being replaced with explicit, machine-readable error codes as part of ongoing API hardening. Customers affected by the window were contacted directly.

Building on Sozuri?

For real-time delivery status payloads and status code reference, see the Webhooks & Status Codes page.

Webhooks & Status Codes Contact support

API Status