domain: just-eat.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register on the Just Eat Takeaway public developers portal at developers.just-eat.com to access JET Connect documentation and apply for partner access
Use the JET Connect Universal API (released May 2024) for new integrations; this replaces older region-specific bespoke integrations and works across all JET markets
Configure a webhook endpoint to receive incoming order payloads from JET; the platform POSTs orders to your registered URL in near real time
Acknowledge each received order by calling the appropriate JET order status update endpoint within the required window to confirm acceptance and provide prep time
Sync menus to JET using the menu management endpoints in the JET Connect API; submit your full menu structure including modifiers and categories
Use the JET sandbox environment at uk.api.just-eat.io for end-to-end testing before requesting production credentials
Known gotchas
JET Connect Universal API is the current standard but regional endpoint paths differ slightly by market (UK, Netherlands, Australia/Menulog, etc.); confirm the correct base URL for each target market
Partner API access is not publicly open; you must apply through the developer portal and be approved before receiving production credentials
Order acknowledgment timeouts are strictly enforced; missing the acceptance window causes automatic cancellation and negatively affects the integration partner's reliability score
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?