Skip to main content
Everything the dashboard does, the API does. If you are running OTO underneath your own system — a storefront, an ERP, a WMS, a marketplace — this is the whole surface.

​
What you can build

The API is organized around the same objects as the product, which means the mental model transfers: an order arrives, it is assigned to a hub, a shipment is booked with a carrier, and the customer is told. Four verbs, 76 endpoints across 20 groups.

​
The shape of an integration

Most integrations are the same five calls, in the same order. The rest of the surface exists for the cases around them.
Step 5 is the one people skipIt is tempting to poll orderStatus on a timer, because it works on day one with no endpoint of your own to host.It stops working at volume: you are making thousands of calls to learn that nothing changed, and the one status you actually needed arrives up to a polling interval late. A webhook is a morning’s work and removes the problem permanently.

​
Where it lives

​
In this section

Authentication

Tokens, headers, the sandbox and plan availability.

REST API reference

All 76 endpoints, with the plan each one needs.

Webhook events

The three event types, payloads and signature verification.

Postman collection

Run every endpoint against the sandbox without writing code.

Errors & rate limits

What failure looks like, and how to handle it.

​
What it connects to

  • Sales Channels — the prebuilt integrations, for when you do not need to build one.
  • Order sync — what happens to an order you push in.
  • Hubs Management — pickup locations, created here as hubs.