Status

Live API availability, current incidents and historical uptime are published on the GrivaOne status portal. Check it first when a request behaves unexpectedly — a broad outage is reported there before anything else.

Checking the API directly

The API exposes an unauthenticated health check outside the versioned prefix. It is the quickest way to confirm the service is reachable from your network:

curl https://gulfpay-production.up.railway.app/health

A 200 response means the API is up. Note this path is /health — it sits outside the /api/v1 prefix, so do not prepend the version.

When your request fails but the API is up

• A 401 means your token is missing or expired — log in again or refresh.
• A 429 means you hit a rate limit — back off and retry.
• A repeatable 5xx with a requestId is worth reporting — see support.
• A request that never completes from a browser is usually a CORS restriction, not an outage.