Skip to content
NexG ConciergeDevelopers

Connect your business to NexG.

Read the merchants, catalogues, delivery zones and events on nexgapp.com, and your own orders, as JSON over HTTPS. Banks send signed payment events back to NexG, in sandbox today, so both sides keep the same record.

Base URLhttps://api.nexgapp.com/v1
curl "https://api.nexgapp.com/v1/zones"
{
  "ok": true,
  "data": {
    "items": [
      {
        "id": "7f1e2d3c-4b5a-4968-8776-655443322110",
        "city_id": "c1a5e2d4-7b3f-4e8a-9c6d-2f1b0e4a8d37",
        "name": "Kilimani",
        "tier": "core",
        "eta_min": 20,
        "eta_max": 30,
        "cod_allowed": true,
        "west": 36.765,
        "south": -1.3,
        "east": 36.8,
        "north": -1.27
      },
      {
        "id": "8a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
        "city_id": "c1a5e2d4-7b3f-4e8a-9c6d-2f1b0e4a8d37",
        "name": "Westlands",
        "tier": "core",
        "eta_min": 25,
        "eta_max": 35,
        "cod_allowed": true,
        "west": 36.795,
        "south": -1.275,
        "east": 36.83,
        "north": -1.245
      }
    ],
    "next_cursor": null
  },
  "meta": {
    "api_version": "v1",
    "limit": 100
  }
}

No key needed for public reads. Example responses, shortened.

From first request to live

  1. Try it without a key

    Public data answers anyone. Run the request above, or any read in the reference.

    Quickstart
  2. Get a key

    Sign in to the developer console with your NexG account. Choose public data, your merchant’s orders, or both. The key is shown once.

    Developer console
  3. Go live

    Keep the key on your server, handle errors and limits, and follow cursors. Banks and partner systems connect in sandbox first.

    Environments

Every endpoint

Full reference

Every endpoint on api.nexgapp.com today is a read, so trying them changes nothing. Writes are listed as they are designed, marked coming soon until they ship.