How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Just Eat Consumers API

The Consumers API from Just Eat — 4 operation(s) for consumers.

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

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

This API exposes 7 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.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.

7 operations 4 paths 11 schemas 1 DELETE3 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.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 Consumers 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 7

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

Consumers 7
GET
/consumers/{tenant}
Get consumers details
4 params → 200400404500501
POST
/consumers/{tenant}
Create consumer
1 param body → 201400403404409500
GET
/consumers/{tenant}/me/communication-preferences
Get communication preferences
1 param → 200401403404500
GET
/consumers/{tenant}/me/communication-preferences/{type}
Get channel subscriptions for a given consumer's communication preference type
2 params → 200401403404500
PUT
/consumers/{tenant}/me/communication-preferences/{type}
Set only the channel subscriptions for a given consumer's communication preference type
2 params body → 204401404500
DELETE
/consumers/{tenant}/me/communication-preferences/{type}/subscribedChannels/{channel}
Remove subscription of a specific communication preference channel
3 params body → 204401404500
POST
/consumers/{tenant}/me/communication-preferences/{type}/subscribedChannels/{channel}
Subscribe to a specific communication preference channel
3 params body → 204401403404500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are ConsumerCreate (6 properties), ConsumerCreateResponse (2 properties), ChannelSubscriptionsWithDerivedField (2 properties), 500ErrorSchema (1 property). Each schema is shown below with its type and property counts.

ConsumerCreateResponse
object
2 properties 2 required
5XXErrorSchema
object
A HTTP 5xx error response
1 property
500ErrorSchema
object
A HTTP 500 error response
1 property
CommunicationTypes
string
ConsumerCreate
object
6 properties 3 required
4XXErrorSchema
object
A HTTP 4xx error response
1 property
ChannelSubscriptions
object
1 property
consumerMarketingPreference
array
CommunicationChannels
string
CommunicationPreferences
object
1 property
ChannelSubscriptionsWithDerivedField
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

just-eat-consumers-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 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
Just Eat Order Delivery Webhooks API
Where this information came from

This is an independent, third-party profile of Just Eat Consumers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.