domain: wolt.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Receive a development Bearer token from Wolt during integration onboarding; use it as your Authorization: Bearer header for all sandbox requests
Confirm that your venue (pickup location) is pre-configured in Wolt's operational tools; the recommended integration flow assumes venues are pre-configured rather than dynamically specified per request
POST to the Wolt Drive deliveries endpoint with customer order information, dropoff address, contact details, and item manifest
Parse the response to obtain the delivery ID and any estimated delivery time provided
Use Wolt Drive webhooks (configured at developer.wolt.com) to receive real-time delivery status updates throughout the lifecycle
Upon successful testing, request a production Bearer token from Wolt; do not use the development token in production
Known gotchas
Wolt Drive requires a commercial agreement with Wolt before any credentials are issued; there is no public self-serve registration for API access
The development token provided by Wolt is only valid in the sandbox environment and must be replaced with a production token before going live
Wolt Drive coverage is limited to Wolt's operating markets in Europe and select other regions; verify coverage availability for each delivery country before building integrations
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?