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 Order Acceptance Webhooks API

The Order Acceptance Webhooks API from Just Eat — 5 operation(s) for order acceptance webhooks.

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

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

5 operations 5 paths 8 schemas 4 POST1 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 Order Acceptance Webhooks 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 5

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

Order Acceptance Webhooks 5
POST
/acceptance-requested
Acceptance requested
body → 200
POST
/order-accepted
Order accepted
body → 200
POST
/order-cancelled
Order cancelled
body → 200
POST
/order-rejected
Order rejected
body → 200
PUT
/redelivery-requested
Customer Requested Redelivery
body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are acceptance-requested (14 properties), order-rejected (4 properties), order-address (4 properties), attempted-delivery-response-received (4 properties). Each schema is shown below with its type and property counts.

order-rejected
object
4 properties
order-item
array
order-item-restriction
object
1 property
acceptance-requested
object
14 properties
order-address
object
4 properties
order-accepted
object
3 properties
order-cancelled
object
3 properties
attempted-delivery-response-received
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

just-eat-order-acceptance-webhooks-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 API API
Just Eat Order Delivery API API
Just Eat Order Delivery Webhooks API