API Access

What a Future API Would Cover

Orda already runs on a real order and delivery pipeline internally — vendor catalogues, live order status, and driver dispatch across Ibadan and Osogbo. A public API isn't built yet, but the most likely first integrations we'd support are:

• Order status webhooks for partners who need real-time delivery updates.
• Read access to a vendor's own catalogue and order history for point-of-sale integrations.
• Delivery-fee and coverage-area lookups for platforms comparing delivery options.

None of this is committed or scheduled — if one of these matches what you're building, telling us helps us prioritize.

Why There's No API Yet

Orda is still early — two cities, a small and growing vendor list, and a team that's mostly focused on getting the core ordering and delivery experience right before opening it up to outside developers. A public API is a real commitment: once other people's software depends on an endpoint, changing it becomes a lot more expensive than changing an internal one. We'd rather ship that when there's an actual integration partner it needs to support, not speculatively ahead of demand.

If you're building something that genuinely needs one — a POS system, a delivery aggregator, a logistics partner — that's exactly the kind of real demand that would move this forward. Vague interest is useful too, but a specific use case is what actually helps us prioritize which endpoints to build first.