Where to find it: Settings → Developers → API Documentation — Open in OTO ↗
What the API is for
OTO already knows, for a given origin, destination and parcel, which carriers will take it, what each will charge you, and how long each usually takes. The checkout API exposes that to your storefront at the moment it matters — while the customer is deciding. This is the same engine that carrier selection uses internally. The difference is only who is asking.Requesting options
POST /rest/v2/checkOTODeliveryFee
What comes back
A list of delivery options, one per carrier service that will accept the shipment.Estimated delivery and pickup times
The two time fields answer different questions, and both belong on a checkout. Average delivery time is the duration: how long this service usually takes on this lane. Pickup cut-off time is the deadline: order after it and the clock starts tomorrow.Putting it on a checkout
- The customer enters a delivery address.
- Your storefront calls
checkOTODeliveryFeewith that city, the cart’s weight, and the hub you would ship from. - You present the options you want to offer — usually cheapest and fastest rather than all of them — with the estimate and, where it is close, the cut-off.
- The customer’s choice becomes the delivery option on the order, so fulfillment ships what was actually sold.
Show fewer options than you receiveA response with nine carriers is a list to choose from, not a menu to display. Checkouts convert worse when shipping becomes a decision with nine branches.Two or three named by outcome — Standard, arrives Tuesday and Express, arrives tomorrow — use the same data and ask less of the customer.
Related
- Carrier integration — the carriers these options come from.
- Shipping automation — how a carrier is chosen when nobody is asked.
- Hubs Management — the origin the estimate is measured from.

