Just Eat UK

Name: Just Eat UK API
Brand: Just Eat UK
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey, oauth2, basic, bearer98 EndpointsREST

For Agents

Drive Just Eat UK marketplace operations: manage checkouts and delivery pools, fetch fees and estimates, update consumer preferences, and respond to async order webhooks.

Install Jentic One Beta

Connect the Just Eat UK to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Just Eat UK, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Just Eat UK API.

Get and update consumer profiles plus communication preferences via /consumers/{tenant} and /consumers/{tenant}/me/communication-preferences

Create, list, modify, and delete delivery pools through /delivery/pools and /delivery/pools/{deliveryPoolId}

Set per-pool availability and daily hours via /delivery/pools/{deliveryPoolId}/availability/relative and /hours

GET STARTED

Start building with Just Eat UK API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Just Eat UK, keeping it validated and agent-ready. The Just Eat UK 'main' API is the partner and consumer surface for the UK marketplace and shares scope with the just-eat-uk slug. Across 98 endpoints it covers checkouts, consumer profiles and communication preferences, delivery pools, delivery fees and estimates, and async webhook callbacks for events such as acceptance-requested and delivery-failed. Auth uses partner JE-API-KEY headers for partner endpoints and JWT bearer tokens for consumer flows.

Use Cases

Patterns agents use Just Eat UK API for, with concrete tasks.

★ Marketplace Checkout Embed

Storefronts that embed Just Eat checkouts call GET /checkout/{tenant}/{checkoutId} to load the order, GET /checkout/{tenant}/{checkoutId}/fulfilment/availabletimes for slot options, and PATCH /checkout/{tenant}/{checkoutId} once the customer confirms. This keeps slot accuracy and total price aligned with the real Just Eat backend rather than a stale snapshot.

Load checkout 'co-501' on tenant 'uk', call GET /checkout/uk/co-501/fulfilment/availabletimes, then PATCH /checkout/uk/co-501 with the chosen time slot.

Delivery Pool Lifecycle for Restaurant Groups

Multi-site restaurant groups manage their own driver fleets through delivery pools. POST /delivery/pools creates a pool, PUT /delivery/pools/{deliveryPoolId}/hours configures daily windows, DELETE /delivery/pools/{deliveryPoolId}/restaurants removes restaurants, and PATCH /delivery/pools/{deliveryPoolId} updates pool config. This puts the daily roster in code rather than in the partner dashboard.

For pool 'pool-77', call PUT /delivery/pools/pool-77/hours with start '12:00' and end '23:30', then PATCH /delivery/pools/pool-77 to add a new restaurant.

Async Webhook Compliance

Just Eat dispatches certain partner events as async webhooks that must return 202 Accepted then post a follow-up Success or Failure payload to the supplied callback URL. Implementing this pattern correctly for /acceptance-requested and /delivery-failed prevents Just Eat from retrying excessively and keeps order timelines accurate.

On POST /acceptance-requested with a callback querystring, return 202 Accepted, run the local accept-or-reject logic, then POST {returnUrl} with status 'Success' or 'Failure'.

Agent-Driven Partner Configuration

An AI ops agent for a restaurant group can adjust delivery pools, hours, and consumer-facing communications via Jentic. The agent searches 'modify a delivery pool', loads PATCH /delivery/pools/{deliveryPoolId}, and executes with the partner JE-API-KEY held in Jentic. Configuration changes that took dashboard taps now happen through chat.

Through Jentic, search 'modify a delivery pool', load PATCH /delivery/pools/{deliveryPoolId}, and execute with deliveryPoolId 'pool-77' to extend operating hours by one hour.

Key Endpoints

98 endpoints — jentic publishes the only available openapi specification for just eat uk, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/checkout/{tenant}/{checkoutId}

Get an in-progress checkout

PATCH

/checkout/{tenant}/{checkoutId}

Update an in-progress checkout

GET

/checkout/{tenant}/{checkoutId}/fulfilment/availabletimes

Get available fulfilment times

POST

/delivery/pools

Create a delivery pool

PATCH

/delivery/pools/{deliveryPoolId}

Modify a delivery pool

PUT

/delivery/pools/{deliveryPoolId}/hours

Set daily operating hours for a delivery pool

GET

/delivery-fees/{tenant}

Get restaurant delivery fees

GET

/delivery/estimate

Get a delivery estimate

GET

/checkout/{tenant}/{checkoutId}

Get an in-progress checkout

PATCH

/checkout/{tenant}/{checkoutId}

Update an in-progress checkout

GET

/checkout/{tenant}/{checkoutId}/fulfilment/availabletimes

Get available fulfilment times

POST

/delivery/pools

Create a delivery pool

PATCH

/delivery/pools/{deliveryPoolId}

Modify a delivery pool

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Just Eat partner JE-API-KEY headers and consumer JWTs are stored in Jentic's encrypted vault and injected at request time. Agents call Just Eat with scoped session access only, never the raw partner key.

Intent-based discovery

Agents search by intent (e.g. 'modify a delivery pool' or 'get delivery estimate') and Jentic returns the matching Just Eat operation with its input schema, so the agent skips browsing the 98-endpoint reference.

Time to first call

Direct Just Eat integration: 1-2 weeks to handle partner auth, the async-webhook callback pattern, and the delivery-pool lifecycle. Through Jentic: under 1 hour to search, load, and execute the first call.

FAQs

Specific to using Just Eat UK API through Jentic.

Why is there no official OpenAPI spec for Just Eat UK?

Just Eat does not publish a public OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Just Eat UK via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Just Eat UK API use?

Partner endpoints use a JE-API-KEY header (Authorization: JE-API-KEY <key>) and consumer endpoints use a JWT bearer token. Jentic stores both credential types in the encrypted vault and supplies them at execution time.

Can I create and manage delivery pools with the Just Eat UK API?

Yes. POST /delivery/pools creates a pool, PATCH /delivery/pools/{deliveryPoolId} updates it, PUT /delivery/pools/{deliveryPoolId}/hours sets daily operating hours, and DELETE /delivery/pools/{deliveryPoolId}/restaurants removes restaurants from the pool.

What are the rate limits for the Just Eat UK API?

Rate limits are negotiated per partner agreement; the spec does not enumerate fixed values. Treat 429 responses with exponential backoff and stagger pool-availability updates.

How do I get a delivery estimate with the Just Eat UK API through Jentic?

Search Jentic for 'get delivery estimate', load GET /delivery/estimate, and execute with the postcode and restaurant identifiers. Jentic resolves auth and returns the estimate to display in your checkout.

How should I respond to async webhooks?

Return 202 Accepted immediately, perform the long-running operation locally, then POST the supplied returnUrl with a JSON body containing status 'Success' or 'Failure' and any webhook-specific data.

Just Eat UK

Connect the Just Eat UK to your agent

Capabilities

Start building with Just Eat UK API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs