Skip to content
E-commerce platforms

just-eat.co.uk

Just Eat UK sandbox and mock API

# Just Eat API Just Eat offers services for our various business partners and our consumer applications. How you interact with the API depends on the services you wish to interact with. ## Security ### HTTPS All api calls and callbacks require HTTPS. Your service will need a valid SSL certificate and be accessible via the standard SSL port (port 443). ## Making an API request Some API calls requir Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
98
Collections
-
Event types
-
Start this simulation
example request
curl https://your-just-eat-uk.slurry.io/delivery/estimate \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 98.

  • POST/acceptance-requested
  • PUT/attempted-delivery-query-resolved
  • GET/checkout/{tenant}/{checkoutId}
  • PATCH/checkout/{tenant}/{checkoutId}
  • GET/checkout/{tenant}/{checkoutId}/fulfilment/availabletimes
  • GET/consumers/{tenant}
  • POST/consumers/{tenant}
  • GET/consumers/{tenant}/me/communication-preferences
  • GET/consumers/{tenant}/me/communication-preferences/{type}
  • PUT/consumers/{tenant}/me/communication-preferences/{type}
  • POST/consumers/{tenant}/me/communication-preferences/{type}/subscribedChannels/{channel}
  • DELETE/consumers/{tenant}/me/communication-preferences/{type}/subscribedChannels/{channel}