Complete the Uber Eats integration activation flow for the target merchant store in the Uber Developer Dashboard.
Authenticate with a valid OAuth token bearing the eats.pos_provisioning scope.
POST to the /eats/stores/{store_id}/posdata endpoint with your integration configuration payload, which tells Uber Eats which POS provider is active for that store.
Uber Eats validates the configuration and activates the POS integration channel for the store; from this point, new orders for that store will be routed via POS webhook rather than the tablet.
Confirm activation by placing a test order in the Uber Eats sandbox environment and verifying your webhook endpoint receives the order notification.
For multi-location rollouts, repeat the posdata activation per store ID; batch automating this via a provisioning script reduces manual effort.
Known gotchas
The posdata activation endpoint is part of the partner-gated integration activation flow; access requires completing Uber Eats's POS integration onboarding, which includes a 99% injection success rate requirement in production.
Activating POS integration for a store disables the Uber Eats restaurant tablet for order management at that location; ensure the POS-side integration is fully tested and stable before activating on live stores.
Store IDs in Uber Eats are UUIDs assigned by Uber and are separate from your internal location identifiers; maintain a mapping table between Uber store UUIDs and your own location IDs before running bulk activations.
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