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 Restaurant OrderTimes API

The Restaurant OrderTimes API from Just Eat — 2 operation(s) for restaurant ordertimes.

Just Eat Restaurant OrderTimes 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 Restaurant OrderTimes. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 4 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.

2 operations 2 paths 4 schemas 1 GET1 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 Restaurant OrderTimes 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 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Restaurant OrderTimes 2
GET
/restaurants/{tenant}/{restaurantId}/ordertimes
Get the restaurant's delivery and collection lead times
GetOrderTimes 3 params → 200401403500
PUT
/restaurants/{tenant}/{restaurantId}/ordertimes/{dayOfWeek}/{serviceType}
Update the restaurant's delivery and collection lead times
UpdateOrderTime 5 params body → 204400401403500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are orderTime (4 properties), updateOrderTimeRequest (2 properties), 4XXErrorSchema (1 property), 500ErrorSchema (1 property). Each schema is shown below with its type and property counts.

500ErrorSchema
object
A HTTP 500 error response
1 property
updateOrderTimeRequest
object
Request object for order time update
2 properties
orderTime
object
The object representing order time entry
4 properties
4XXErrorSchema
object
A HTTP 4xx error response
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

just-eat-restaurant-ordertimes-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