Sozuri Developer Documentation

Real-time operational status of each Sozuri service and 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.

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 service status. One of `operational`, `degraded`, `down`.
`carriers.*`	string	Per-carrier routing status (`safaricom`, `airtel`, `telkom`).
`components.database`	string	Status of the primary database connection.
`components.cache`	string	Status of the Redis cache and queue layer.
`version`	string	API / application version.
`timestamp`	string	ISO-8601 timestamp of the probe.

Status values

Value	Meaning	Recommended action
operational	Component is up and healthy.	Proceed.
degraded	Reachable but a non-critical signal is anomalous.	Submission likely to succeed; consider deferring large bursts.
down	Component is unreachable.	Do not initiate a scheduled run; wait and re-probe.
unknown	Status could not be determined.	Treat as degraded.

HTTP semantics:

200 — submissions can be attempted. Overall status is operational or degraded.
503 — core infrastructure (database / cache) is unreachable. 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

Platform

Service	Status
SMS	UP
SMPP	UP
OTP / Authy	UP
WhatsApp Channels	UP
OmniChannel API	UP
Airtime	DOWN
Billing	UP
Debugging & Alerts	UP
Documentation	UP
Customer Support	UP

Carrier connectivity

Service	Status
SMS Shortcode (Kenya)	UP
SMS Sender ID (Kenya)	UP

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 support@sozuri.net 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