Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Just Eat Restaurants API

The Restaurants API from Just Eat — 15 operation(s) for restaurants.

Just Eat Restaurants API is one of 24 APIs that Just Eat publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Restaurants. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 18 operations across 15 paths, and defines 43 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against 3 base URLs: https://uk.api.just-eat.io, https://i18n.api.just-eat.io, https://aus.api.just-eat.io.

18 operations 15 paths 43 schemas 14 GET4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://uk.api.just-eat.io
Authentication
HTTP Bearer, API Key, HTTP Basic, OpenID Connect, HTTP Bearer
Resource Areas
1

Authentication & Security 5

Just Eat Restaurants API declares 5 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). An API key is passed in the header as Authorization (api_key). It accepts HTTP basic authentication (basic_auth). It supports OpenID Connect (justeat_adfs) discovered at https://adfs.just-eat.com/adfs/.well-known/openid-configuration. It accepts HTTP bearer tokens (JWT token with payload `RestaurantId` and Role `[RestaurantRead | VerifyEmail | RestaurantWrite | FullAccess | DocumentRead]`) (restaurantsignup_jwt).

  • Bearer — Bearer token authentication using a JSON Web Token (JWT).
  • api_key — APIs for delivery partners require an API key that will have been issued to you.
  • basic_auth — A few services allow the use of basic authentication when a partner doesn't support OAuth based authentication.
  • justeat_adfs — ADFS authentication provider for internal Just Eat tools.
  • restaurantsignup_jwt — Bearer token authentication using a JSON Web Token (JWT), used by the restaurant sign up system

Paths & Operations 18

Across 15 paths, the API surfaces 18 operations — 14 GET, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Restaurants 18
GET
/restaurants/bylatlong
Get restaurants by location
SearchByLocation 7 params → 200400401500
GET
/restaurants/bypostcode/{postcode}
Get restaurants by postcode
SearchByPostcode 6 params → 200400401500
PUT
/restaurants/driver/eta
Set ETA for pickup
body → 202400
GET
/restaurants/{tenant}/{restaurantId}/catalogue
Get product catalogue
2 params → 200404500
GET
/restaurants/{tenant}/{restaurantId}/catalogue/availabilities
Get all availabilities
4 params → 200400404500
GET
/restaurants/{tenant}/{restaurantId}/catalogue/categories
Get all categories
4 params → 200400404500
GET
/restaurants/{tenant}/{restaurantId}/catalogue/categories/{categoryId}/items
Get all category item IDs
5 params → 200400404500
GET
/restaurants/{tenant}/{restaurantId}/catalogue/items
Get all menu items
4 params → 200400404500
GET
/restaurants/{tenant}/{restaurantId}/catalogue/items/{itemId}/dealgroups
Get all menu item deal groups
5 params → 200400404500
GET
/restaurants/{tenant}/{restaurantId}/catalogue/items/{itemId}/dealgroups/{dealGroupId}/dealitemvariations
Get all deal item variations for a deal group
6 params → 200400404500
GET
/restaurants/{tenant}/{restaurantId}/catalogue/items/{itemId}/modifiergroups
Get all menu item modifier groups
5 params → 200400404500
GET
/restaurants/{tenant}/{restaurantId}/catalogue/items/{itemId}/variations
Get all menu item variations
5 params → 200400404500
GET
/restaurants/{tenant}/{restaurantId}/fees
Get Restaurant Fees
3 params → 200400401403404500
PUT
/restaurants/{tenant}/{restaurantId}/fees
Create or Update Restaurant Fees
3 params body → 200400401403404500
GET
/restaurants/{tenant}/{restaurantId}/menu
Get the latest version of the restaurant's full menu
3 params → 301400401403500
PUT
/restaurants/{tenant}/{restaurantId}/menu
Create or update a menu
putMenuForIngestion 4 params body → 202400401403500
GET
/restaurants/{tenant}/{restaurantId}/servicetimes
Get service times
getRestaurantServiceTimes 2 params → 200403404500
PUT
/restaurants/{tenant}/{restaurantId}/servicetimes
Create or update service times
putRestaurantServiceTimes 2 params body → 200400403500

Schemas 43

The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are SearchRestaurant (78 properties), SearchResponse (10 properties), Variation (9 properties), ServiceTimesDays (7 properties). Each schema is shown below with its type and property counts.

MenuItemBase
object
6 properties
Time
object
3 properties
PagedMenuModifierGroupsResponse
MenuDealGroup
local-date-time
string
A local date time object, conforming to ISO-8601, but with only a partial time representation and no time offset.
ServiceTimesCollection
array
Menu
PagedAvailabilitiesResponse
ServiceTimesDays
object
The desired times at which a restaurant is in service
7 properties
ServiceTypeFeeConfiguration
object
Distinct values which are configured for a particular service type
1 property
MenuIngestionResponse
object
1 property
DealItemVariation
object
4 properties
Fee
object
The object which encapsulates a Fee
2 properties
Availability
object
5 properties
MenuDealGroupBase
object
3 properties
PagedCategoryItemsResponse
SearchRestaurant
object
78 properties
ExternalSearchResponse
object
1 property
IgnoredRestaurantIds
object
1 property
RestaurantPromotedPlacementInfo
object
2 properties
RestaurantFees
object
An object encapsulating all possible fees which a restaurant can apply to itself
1 property
ServiceTimesServices
object
2 properties
PagedMenuItemsResponse
ServiceTimes
object
1 property
PagedDealItemVariationResponse
PagedAfterOnlyCursorResponse
object
1 property
PagedVariationsResponse
MenuItem
SearchResponse
object
10 properties
MenuBase
object
4 properties
4XXErrorSchema
object
A HTTP 4xx error response
1 property
PagedMenuDealGroupsResponse
Category
Variation
object
9 properties
CategoryBase
object
3 properties
RestaurantETAs
array
MenuModifierGroup
object
5 properties
500ErrorSchema
object
A HTTP 500 error response
1 property
PagedCategoriesResponse
MenuModifier
object
5 properties
ConsumerErrorResponse
object
2 properties
SearchWebResponse
object
3 properties
RestaurantDeliveryFees
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

just-eat-restaurants-api-openapi.yml Raw ↑

Other APIs Just Eat publishes across the network.

Just Eat Attempted Delivery API API
Just Eat Attempted Delivery Webhooks API
Just Eat Checkout API
Just Eat Consumer Queries Webhooks API
Just Eat ConsumerQueries API
Just Eat Consumers API
Just Eat Delivery Pools API API
Just Eat DeliveryFee API
Just Eat Order Acceptance API API
Just Eat Order Acceptance Webhooks API
Just Eat Order API API
Just Eat Order Delivery API API