Contact Otter to access developer documentation and obtain API credentials for the open API integration program
When Otter pushes an aggregated order to your POS or middleware via its integration, extract the Otter order ID and the originating platform identifier from the inbound payload
After the POS accepts the order, call the Otter API to update the order status to accepted or confirmed, including the expected preparation time so the delivery platform can dispatch a courier at the right time
As the order progresses (for example, food ready, picked up), send subsequent status updates to Otter using the Otter order ID; Otter will relay these to the originating delivery platform
Handle cancellation events from Otter — which may originate from the delivery platform or the customer — by voiding or canceling the corresponding ticket in the POS and confirming the cancellation back to Otter
Use Otter's reporting API or dashboard to reconcile order counts and error rates across channels for operational visibility
Known gotchas
Otter's open API is intended for technology partners, not direct restaurant access; API credentials and endpoint details require a formal partner agreement
Otter aggregates from many delivery platforms, but not every platform supports all order lifecycle status updates via Otter; check per-platform capabilities in the Otter documentation
Prep time communicated back to Otter affects courier dispatch timing on delivery platforms; inaccurate prep times cause early arrivals and order wait issues
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp