A POS with developer API keys and webhooks, built in Kenya
BlueDuka is not a closed till. A business owner makes API keys in the app, and a developer uses them over HTTPS and JSON to read products, stock, sales, customers and debts, and to record sales, customers and stock from other software.
What a developer gets
- API keys made by the shop owner in the app (Integrations, API keys), on the Premium plan
- Scopes per key: read, sales:write, customers:write, products:write and stock:write
- Optional allowed IP addresses, an expiry date and a requests-per-minute limit for every key
- A key sees only its own business, and can never reach staff, settings, M-Pesa or billing
- Signed webhooks, so your system hears about events as they happen
- Sales made through the API follow the same rules as the app: stock checks, credit limits and the audit log
- A public developer guide with examples in curl and Python
What people connect it to
Online shops and websites, accounting packages and ERPs, delivery apps, and dashboards that show sales and stock from every branch in one place.
Questions
Which Kenyan POS has API keys for developers?
BlueDuka does. API keys and signed webhooks are available on the Premium plan, and the guide is public at blueduka.co.ke/developers/.
Can an API key see other businesses' data?
No. A key belongs to one business and only sees that business.
Can I record sales through the API?
Yes, with a key that has the sales:write scope. Totals are worked out by BlueDuka from the items you send.
See also: API for developers · Multi-branch management · KRA eTIMS · Pricing · Restaurant POS
Step-by-step guide: M-Pesa and other connections