OmnioIQ · Solutions

Build on the public API.

Connect a client's order, warehouse or finance systems to OmnioIQ. The API is documented, the webhooks are signed, and each workspace has its own docs page.

API integration settings for a workspace, keys masked

Public API

Version 1, one route set.

Create and read bookings, drivers, vehicles, depots, zones, routes and tracking. Call the optimise endpoint to plan a set of bookings.

Access uses tokens from your workspace sign-in.

The workspace API docs page listing the /api/v1 routes
Webhook settings: endpoint, events and delivery history

Webhooks

Hear about changes as they happen.

Register a webhook and OmnioIQ calls it when a booking changes. Each call is signed with HMAC, and failed calls are retried.

Per client

A workspace, a brand, a docs page.

Each client has its own workspace with its own logo and colour. The docs page and API settings sit inside it, so you can hand a client what they need and nothing more.

Branding settings for a client workspace

Let AgentQ run a month of your routes.

You get an ROI report at the end with your numbers, measured on your operation.

Try it on your routesOne month, up to five drivers, before you sign anything.
Published pricingTiers on the site. No add-on menu, no annual lock-in.
We don't compete with youNo delivery service of our own, no shared customers.
Talk to the buildersYour account lead knows the code and the routes.
Pilot report: on-time rate, cost per drop and share of decisions made by AgentQ