Automate merchant activation using the Grubhub Onboarding API
domain: developer.grubhub.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Implement OAuth-based merchant authentication so a merchant can securely link their existing Grubhub account to your platform
Call the merchant-discovery endpoint to retrieve all Grubhub locations associated with the authenticated merchant's account
Call the eligibility-validation endpoint to determine which of those locations can actually be integrated with your platform
Complete the self-service onboarding flow, which Grubhub states can finish in 5-10 minutes versus the 7-10 day manual process
Follow the Onboarding API troubleshooting guide for common activation failures, and consult the best-practices doc for handling merchants switching integration providers
Known gotchas
Onboarding API access is part of Grubhub's Partner Integration V2 program — it isn't automatically available to every Marketplace/Order Taking API partner without separate enablement
Eligibility validation can reject locations for reasons outside your control (e.g. existing exclusivity agreements) — design onboarding UX to handle partial/rejected location sets gracefully
Merchants mid-migration from another provider need careful handling per the best-practices guide to avoid integration downtime during the switch
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?