Introduction
Connect a point-of-sale system to Nunua Pro. A shop's products, prices and stock stay in sync with its storefront, out-of-stock items disappear by themselves, and the orders customers place online arrive in the POS. One generic API, whether the POS runs in the cloud or on the shop's own computer.
What you can build
Catalogue sync
Products with prices, stock, variations, barcodes and photos. Send only what changed, on every sale.
Online orders
Orders reach your POS by webhook, or by a feed a locally installed POS can poll.
Code linking
The owner types a short code from your till into our app. No keys are copied by hand.
How it fits together
- Get a partner keyIt identifies your company. Create a developer account and make it in the console.
- Build in the sandboxOne call gives you a hidden test shop. Sync a catalogue and simulate customer orders with no real shop or customer involved. The quickstart takes about ten minutes.
- Link real shopsShow a link code on the till; the owner types it into the Nunua Pro Business app; your POS collects that shop's key. See linking a shop.
- Go liveSend each shop's catalogue, keep it fresh, take orders, and watch your shops' sync health from the partner API.
Base URL and format
https://nunuapro.app/api| Prefix | Used with | For |
|---|---|---|
/pos/v1 | A shop key | Everything a POS does day to day for one shop: products, stock, orders. |
/pos-partner/v1 | Your partner key | Link codes, the sandbox, and the health and sales of all your shops. |
Requests and responses are JSON in UTF-8. Money is in Tanzanian shillings (TZS), as numbers. Timestamps are ISO 8601 with an offset, for example 2026-11-03T10:15:00+03:00.
Cloud or local POS
Both kinds work, and every feature is available both ways.
- A cloud POS can receive webhooks, so orders arrive the moment a customer commits.
- A locally installed POS can't be reached from the internet. It pushes changes to us and polls the event feed for orders. When it has been offline, it catches up safely: late updates never overwrite newer data.
Good to know
- Nothing goes live by surprise. Imported products start hidden until the shop owner approves them, or chooses to list everything.
- Messy data is expected. ALL-CAPS names are tidied for the storefront (your original is kept), junk barcodes are ignored, and a row with absurd numbers is rejected on its own without failing the batch.
- Nothing is deleted. A product that leaves your POS is archived, so order history survives.
- Safe to retry. Writes accept an
Idempotency-Key. - Extras and variations. Orders carry the variation a customer chose and any add-ons (extra cheese, a sauce), priced per unit.