Choose between Toast Delivery Services (TDS) and first-party delivery when building a Toast delivery integration
domain: doc.toasttab.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Decide between Toast Delivery Services (TDS), which dispatches on-demand couriers via Uber Direct or DoorDash Drive under the hood, and first-party delivery using the restaurant's own drivers — Toast does not allow running both simultaneously for the same restaurant
For first-party delivery integrations, call the /diningOptions endpoint of the Configuration API to identify which dining option GUIDs have DELIVERY behavior
Ensure the integration only creates/updates orders whose diningOption resolves to DELIVERY behavior when building delivery-specific logic
When assigning a delivery driver from the restaurant's own staff, PATCH the /deliveryInfo endpoint of the Orders API with the Toast platform GUID of the employee assigned as driver
If using TDS instead, configure it through the Toast Online Ordering dashboard rather than the Orders API, since TDS dispatch is handled by Toast's Uber Direct/DoorDash Drive backend, not a Toast-exposed dispatch endpoint
Known gotchas
TDS and first-party ('your own drivers') delivery are mutually exclusive per restaurant in Toast's configuration — an integration built assuming both can run together will conflict with the dashboard setting
Dining option behavior (DELIVERY) must be looked up via the Configuration API rather than assumed from a dining option's display name, since restaurants can name/reuse dining options differently
TDS dispatch logic (courier assignment, ETAs) lives inside Uber Direct/DoorDash Drive's systems, not a Toast-native dispatch API — troubleshooting a TDS delivery problem may require Toast support rather than a Toast API response
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?