Waymark / Routes / ifood-partner-api Receive and confirm a marketplace order from iFood via the Partner API webhook
domain: ifood-partner-api · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Register an application in iFood's developer portal and complete OAuth2 client-credentials auth plus the required homologation (certification) process Configure a single webhook URL (max 250 chars) to receive order events from the Events module Handle the PLACED event when a new order arrives, then call the confirm endpoint to accept it Deduplicate events using the event id since delivery is at-least-once with no ordering guarantee Implement a polling fallback (roughly every 5 minutes) in case a webhook delivery is missed Known gotchas Webhooks auto-disable after 72 hours of unresolved critical errors, silently cutting off order flow Events are discarded after about 15 minutes of failed retries, so downstream processing must be fast and idempotent Production access requires passing iFood's homologation review, not just registering an app
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