Migrate a Just Eat Takeaway POS integration from the legacy platform to JET Connect (formerly Flyt)

domain: developers.just-eat.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Confirm whether your current integration uses the legacy Just Eat Takeaway Partner/Order Management API or the older Polygon Central-based order posting model
  2. Review the JET Connect (formerly Flyt) documentation and Universal Integration APIs, the cross-region replacement integration platform
  3. Rebuild catalog/menu push to use JET Connect's catalog endpoints, which add variant support not present in some legacy integrations
  4. Rebuild order pull to use JET Connect's order and customer-info endpoints, including auto-accept configuration if desired
  5. Run both integrations in parallel against a test/staging restaurant before cutting production traffic over, since JET Connect's data model (variants, customer info scoping) differs from the legacy platform

Known gotchas

Related routes

Integrate Just Eat Takeaway Order Management API to receive orders, send confirmations, and push preparation time updates for a POS integration
Just Eat Takeaway · 6 steps · unrated
Integrate with the Just Eat Takeaway partner APIs
just-eat.com · 6 steps · unrated
Connect a restaurant POS to Deliverect as an order aggregator to receive orders from multiple delivery platforms
developers.deliverect.com · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans