Nabd Developersstatus.sd

Built for Sudan. Ready for your code.

Local signals.
Endless possibilities.

Sudan’s bank status, telecom services, and currency rates. One clear API to bring essential data into the products you build.

Start building Explore pricing

REST endpoints. Structured JSON. Your next integration.

events.json · example response
GET/api/open/v1/events
{
  "data": [
    {
      "code": "bank.status.changed",
      "description":
        "A bank service status changed."
    },
    {
      "code": "currency.updated",
      "description":
        "Currency rates were updated."
    }
  ]
}
200 OK · application/jsonAPI v1

Less guesswork. More building.developer.status.sd

RESTSimple by design
JSONStructured responses
KEYServer-side access
HMACSigned webhooks

The building blocks

Essential data.
Thoughtfully connected.

From service availability to currency snapshots, get the signals your users need without piecing together unrelated sources.

  • Service status

    Bank and telecom service states, with stable slugs and per-service status fields.

    GET /dashboard

  • Status history

    Historical bank status intervals. See what changed and when each interval began.

    GET /banks/{slug}/history

  • Currency rates

    Currency snapshots with bank rates, parallel rates, and source detail links.

    GET /currency

  • Change events

    Discover available events and subscribe to signed webhook deliveries.

    GET /events

From idea to integration

A familiar API.
A straightforward start.

Keep your API key on your server, call a versioned endpoint, and build with documented JSON responses.

Explore the documentation
  1. 01

    Choose your access

    Compare plans, then sign in to manage your subscription and API keys.

  2. 02

    Make your first request

    Send your key in the X-API-Key header from your server.

  3. 03

    Stay in sync with webhooks

    Subscribe to change events, verify HMAC-SHA256 signatures, and handle deliveries idempotently.

    Read the webhook contract ↗

Designed for change

Signed events.
Predictable delivery.

Each webhook includes a delivery ID, event, creation time, and event data. Failed deliveries follow a bounded retry schedule.

  1. Attempt 1ImmediateSigned POST
  2. Retry 160 secondsAfter failure
  3. Retry 25 minutesAfter failure
  4. Retry 330 minutesFinal attempt

Your next build starts here

Build something that keeps people informed.

Read the docs Developer sign in →