Register as a Dispatch DSP (Delivery Service Provider) partner via the Olo Dispatch partner portal and complete the onboarding process.
Implement the required Dispatch DSP API endpoints on your side: quote, create delivery, and status update endpoints that Olo will call when a restaurant requests delivery through your network.
Configure your DSP credentials and endpoint URLs in the Dispatch portal so Olo knows how to route delivery requests to your service.
When a restaurant triggers a delivery via Olo Dispatch, Olo calls your quote endpoint to retrieve pricing and availability; respond with a valid quote payload.
After the restaurant accepts your quote, Olo calls your create delivery endpoint; dispatch the courier and begin posting status updates back to Olo using the delivery status webhook.
Test the end-to-end flow using Olo's sandbox environment before requesting production activation.
Known gotchas
Olo Dispatch integration is DSP-side; restaurants configure which DSPs are available via Olo's admin tools, not via direct API calls — DSPs must complete the Dispatch partner certification before appearing in the provider list.
Quote responses must include accurate availability and pricing for the requested pickup location; inaccurate quotes that change significantly at dispatch time degrade the restaurant's trust in your DSP and can result in removal from the provider pool.
Status updates from the DSP back to Olo must follow Olo's defined status taxonomy exactly; custom or unmapped statuses will cause display issues in the Olo Dashboard and the restaurant's POS.
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