/justeat/restaurants

POST /api/justeat/restaurants

Price: 20 credits

Get full Just Eat (just-eat.co.uk) restaurant details by seo name (slug) or menu URL: name, address, rating, cuisines, delivery ETA and fees, and the complete menu with categories, items, prices, descriptions, images, calories and modifier groups with options and option prices.

How to use it

Fetch a single Just Eat (just-eat.co.uk) restaurant by its seo name slug (e.g. 'papa-johns---farringdon-london') or a full menu URL. Returns id, name, alias, menu_url, image, cover, description, phone, allergen_url, rating, rating_count, cuisines, address (street/city/postcode/latitude/longitude/country), currency, is_halal, supports_delivery, supports_collection, is_offline, eta_minutes/eta_lower/eta_upper, minimum_order_value, delivery_fee, category_count, item_count, opening_times (per service type, each day with open windows from_time/to_time) and the full menu as categories, each with items (name, description, price, variations with name and price, image, calories, type, is_deal, labels and modifier_groups with options and option prices). Use a restaurant's alias from the search endpoint as the input here.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• restaurant string required — Just Eat restaurant seo name (slug) or a full menu URL (examples: "papa-johns---farringdon-london", "https://www.just-eat.co.uk/restaurants-papa-johns---farringdon-london/menu"; minLength: 1)

Response

• @type string (default: "JusteatRestaurant")
• id string required
• menu_url string required
• name string nullable
• alias string nullable
• image string nullable
• cover string nullable
• description string nullable
• phone string nullable
• allergen_url string nullable
• rating number nullable
• rating_count integer nullable
• cuisines array (default: [])
• address object nullable
  • @type string (default: "JusteatAddress")
  • street string nullable
  • city string nullable
  • postcode string nullable
  • latitude number nullable
  • longitude number nullable
  • country string nullable
• currency string nullable
• is_halal boolean (default: false)
• store_front_type string nullable
• time_zone string nullable
• energy_units string nullable
• supports_delivery boolean (default: false)
• supports_collection boolean (default: false)
• is_offline boolean (default: false)
• eta_minutes number nullable
• eta_lower number nullable
• eta_upper number nullable
• minimum_order_value number nullable
• delivery_fee number nullable
• service_fee_text string nullable
• category_count integer (default: 0)
• item_count integer (default: 0)
• opening_times array (default: [])
  • @type string (default: "JusteatOpeningTimes")
  • service_type string nullable
  • days array (default: [])
    • @type string (default: "JusteatOpeningDay")
    • day string nullable
    • windows array (default: [])
• categories array (default: [])
  • @type string (default: "JusteatMenuCategory")
  • id string required
  • name string required
  • description string nullable
  • image string nullable
  • items array (default: [])
    • @type string (default: "JusteatMenuItem")
    • id string required
    • name string required
    • description string nullable
    • price number nullable
    • variations array (default: [])
    • image string nullable
    • calories string nullable
    • type string nullable
    • is_deal boolean (default: false)
    • labels array (default: [])
    • modifier_groups array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Restaurant not found (well-formed slug but the menu page does not exist) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.