The NexG API

What the API does, who it is for, and the shortest path from a first request to a live integration.

On this page

What the API does

NexG is a concierge delivery and booking platform for Kenya. What a guest sees on nexgapp.com, from verified merchants and their catalogues to delivery zones and events, is also available to your systems as JSON over HTTPS, from https://api.nexgapp.com/v1.

Read NexG's public data: merchants, catalogues, zones, upcoming experiences and bookable services. No key is needed to start.
Read your own orders with a key bound to your merchant, newest first, with the same stage the merchant console shows.
Call back to NexG with signed events. Banks do this today for payments at checkout.

How it fits together

NexG keeps one record of every merchant, item and order in its database. The website, the merchant console and this API all read that same record, so what your system reads is what a guest sees.

Your system

Website, POS, ERP, booking or bank

GET /v1/…

NexG API

api.nexgapp.com · keys, scopes, limits

one record

nexgapp.com

Storefronts in NexG’s own design

Your bank

Signs every event it sends

signed POST

NexG webhook

Checks the signature twice

once per event

The order

Marked paid only by a verified event

Reads go to the API. Events come back to the website's webhook. Both end in the same database.

Who it is for

Merchants

Today. Read your own orders into your back office with a key bound to your merchant, and show your NexG listing and catalogue on your own website.

Coming soon. Book transfers and couriers for your guests through the API, and receive order events instead of polling.

Merchant integration guide

Partners and developers

Today. Build on NexG’s public data: live merchants and catalogues, delivery zones, upcoming experiences and bookable services. Public reads work without a key.

Coming soon. Sandbox keys with test data, for building writes without touching real orders.

Quickstart

Banks and payment providers

Today. Collect payments at checkout through the bank collection contract, with signed webhooks, tested end to end against the NexG Sandbox Bank.

Coming soon. The first live bank connection, once finance has approved limits and reconciliation.

Bank collections

Hotels and stays

Today. Show guests what NexG offers in your city: live merchants and their menus, the zones NexG delivers to, and what is on.

Coming soon. Airport transfers and couriers booked for guests from your own system.

Connecting your systems

Getting started

Make a request without a key: curl https://api.nexgapp.com/v1/zones. The quickstart walks through it.
Sign in to the developer console with your NexG account and issue a key. It is shown once.
Read Authentication, Errors and Rate limits before you go live, then build against the API reference.

Not available yet

These are designed or planned, and each is marked coming soon wherever it appears in these docs. Do not build against them until the changelog says they are live.

Writes: booking a service with POST /v1/orders, and any PATCH endpoint.
Events NexG sends to you, such as an order changing stage. Poll your orders for now.
Sandbox API keys with test data.
Two-way sync with a POS, ERP, booking or inventory system.
OAuth sign-in for third-party apps. Use API keys.

Everything live today is read-only

No endpoint on api.nexgapp.com changes anything at NexG, so you can explore against the live API safely. The first write, booking a service, is designed around an idempotency key, so a retried booking is never made twice.