canonical: https://jentic.com/apis/just-eat.co.uk/just-eat

# Just Eat UK

The Just Eat UK API powers restaurant discovery and the full order lifecycle on the Just Eat marketplace. It searches restaurants by location or postcode, retrieves menus, places orders, and drives order status through acceptance, delivery tracking, and completion for partner integrations. Responses are JSON scoped to a tenant and restaurant, so an agent can find a restaurant, build an order, or update its delivery state.

## For AI agents

Search Just Eat UK restaurants, retrieve menus, place orders, and update order and delivery status across the marketplace.

## Scope

Does not process card payments, run loyalty programs, or manage restaurant accounting; use it for Just Eat restaurant discovery and order operations only.

## Capabilities

- Search restaurants by latitude and longitude or by postcode
- Retrieve a restaurant's menu for a tenant
- Place a new order with a restaurant
- Advance an order through acceptance, rejection, and completion
- Update delivery state such as driver assignment and on-its-way
- Submit restaurant menu ingestion updates for partners

## Use cases

### Restaurant discovery by location

Ordering experiences start with finding places that deliver to the customer. The Just Eat UK API searches restaurants by postcode or coordinates and returns the outlets serving that area, so an application can present available restaurants before a customer commits to an order. Discovery endpoints are open and do not require a partner token.

Example prompt: Search Just Eat UK for restaurants serving a given postcode and return the list of available outlets.

### Place and track an order

A complete ordering flow moves from a built basket to a placed order and then through delivery. The Just Eat UK API places an order and exposes state transitions for acceptance, driver assignment, and delivery, letting an integration keep a customer informed from checkout to arrival. Delivery-state updates identify the order by its identifier.

Example prompt: Place an order for a selected restaurant, then push its delivery state through to delivered.

### Menu management for partners

Restaurant partners keep menus current across price and availability changes. The Just Eat UK API retrieves a restaurant's menu and accepts menu ingestion updates, so a point-of-sale integration can push a refreshed menu without manual re-entry. Menu operations are addressed by tenant and restaurant identifiers.

Example prompt: Retrieve the current menu for a restaurant, apply price changes, and submit the updated menu for ingestion.

### Agent-driven ordering assistant

An AI concierge agent can find food and place an order for a user without a developer wiring each call. Through Jentic the agent matches an intent such as 'order dinner near this postcode' to Just Eat search and order operations, runs them in sequence, and reports status back. Any partner bearer token stays in the user's Jentic One instance and never reaches the agent's prompt.

Example prompt: Search restaurants for a postcode, retrieve a menu, build an order, and place it while reporting the delivery state.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/restaurants/bylatlong` | Search for restaurants near a latitude and longitude. |
| GET | `/restaurants/bypostcode/{postcode}` | Search for restaurants serving a postcode. |
| GET | `/restaurants/{tenant}/{restaurantId}/menu` | Retrieve a restaurant's menu. |
| POST | `/orders` | Place a new order. |
| GET | `/search/restaurants/{tenant}` | Search restaurants within a tenant region. |
| PUT | `/orders/{orderId}/accept` | Accept an incoming order. |
| PUT | `/orders/{orderId}/cancel` | Cancel an order. |

## Key resources

- **Restaurant search** — Find restaurants by postcode or coordinates and search within a tenant.
- **Menus** — Retrieve a restaurant's menu and submit menu ingestion updates.
- **Orders** — Place orders and advance them through acceptance, rejection, and completion.
- **Delivery state** — Update driver assignment, location, and delivery milestones for an order.

## Why Jentic

- **Setup:** Wiring Just Eat yourself means tracking which endpoints are open and which need a partner bearer token, threading tenant and restaurant identifiers through order and menu paths, and following a multi-step delivery-state flow. With Jentic you install once, import Just Eat from the API Directory, and store any token a single time.
- **Permission scoping:** Jentic lets you grant your agent only the Just Eat operations it needs, such as restaurant search and menus without order placement, and enforces that on every call.
- **Credential handling:** Any Just Eat partner token is stored once, encrypted, by your own Jentic One instance. It is injected when a call runs and never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents find Just Eat through Jentic's intent search, matching a request like 'find restaurants for this postcode' to the right operation without hardcoded endpoints.

## Related APIs

- **Delivery Hero** — Point-of-sale integration API for the Delivery Hero food-ordering network.
- **Grubhub** — Food ordering and delivery marketplace API for the US market.
- **Foodkit** — Restaurant commerce platform for menus, orders, and loyalty.

## FAQ

### What can an AI agent do with the Just Eat UK API through Jentic?

An agent can search restaurants by postcode or location, retrieve menus, place orders, and update order and delivery state. Through Jentic the agent matches an intent to the right operation and runs it, with any partner token injected at execution time.

### How do I authenticate with the Just Eat UK API?

Most Just Eat endpoints require no bearer token of their own, so restaurant search, menu retrieval, and order placement are open, while partner operations use a bearer token in the Authorization header. You store any token once in your Jentic One instance, which supplies it on the calls that need it rather than exposing it to the agent.

### Which endpoints are open and which need a token?

Discovery and order-flow endpoints in this specification declare no security requirement, while a small set of partner endpoints carry a bearer token requirement. Check each operation's security in the spec to see whether a token applies before calling it.

### Does the API document rate limits?

The OpenAPI specification does not state rate limits; throughput and partner access depend on your agreement with Just Eat. Confirm the limits for your integration with Just Eat before running high-volume order or menu operations.

### Can I limit what my agent is allowed to do with the Just Eat UK API?

Yes. Jentic lets you allow only the operations your agent needs, for example restaurant search and menu retrieval while withholding order placement and cancellation. Your Jentic One instance enforces that boundary on every call and keeps any token outside the agent's context.