Skip to content
Unicom360
Status and health

Reference

Status and health

GET /health is an unauthenticated endpoint your monitoring can poll to confirm the gateway is up.

GET/health

Confirms the gateway is up. No authentication. No authentication required.

Example request

curl https://api.unicom360.com/health

Responses

200 healthy
{
  "status": "ok",
  "timestamp": "2026-10-22T08:15:30.412Z",
  "version": "0.1.0",
  "environment": "production"
}

If this endpoint answers, the gateway can take requests. It does not check the carrier links; delivery status comes through callbacks and the portal.

What it tells you

A 200 with status: "ok" means the gateway process is up and answering HTTP. version is the gateway build and environment the deployment it answered from. That is the whole contract: it does not test the carrier links or the delivery workers, so a healthy answer here and a message that is slow to deliver are not a contradiction.

Monitoring

  • Poll it from your uptime monitor at a sensible interval; once a minute is plenty. It needs no key and is not counted against any rate limit.
  • Treat anything other than a 200 within a few seconds as the gateway being unreachable, and hold or queue sends until it returns rather than retrying in a tight loop.
  • For the state of individual messages, use the callback_url on each send (see Delivery webhooks) and the portal's reports.