Delivery marketplace research
Mit Just Eat-Endpunkten verwandelst du delivery marketplace research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Just Eat's public UK marketplace into structured JSON — full restaurant listings for a postcode in Just Eat's own default sort order, restaurant profiles, and priced menus with customization option groups. Credential-free.
Search Just Eat restaurants by UK postcode and get full priced menus as structured JSON.
Endpunkt-Familien
2
Dokumentierte Parameter
11
Beispiele
4
Live-Katalog-Snapshot
Aktive Endpunkte
4
Methoden
GET
Pflichtparameter
8
Schema-Referenzen
4
{
"platform": "Just Eat",
"endpoint": "justeat-search",
"method": "GET",
"path": "/justeat/search",
"auth": "apiKey"
}Use Cases
Search Just Eat restaurants by UK postcode and get full priced menus as structured JSON.
Mit Just Eat-Endpunkten verwandelst du delivery marketplace research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Just Eat-Endpunkten verwandelst du uk restaurant menu and pricing monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Just Eat-Endpunkten verwandelst du postcode-level coverage mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Just Eat-Endpunktkatalog — 4 Endpunkte, 11 dokumentierte Request-Parameter und 4 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
4 documented Just Eat endpoints, grouped into 2 request families — Restaurant and Search.
11 request parameters are documented across those Just Eat endpoints, 8 of them required — the full input contract is public before you write any integration code.
4 of the 4 Just Eat endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Just Eat endpoints document their error responses (400, 404 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
4 hosted MCP tools back the Just Eat endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/justeat/restaurant
/justeat/search
Endpunktkatalog
/justeat/searchReturns Just Eat's full restaurant listing for a UK postcode -- every restaurant the site's own area page carries, ordered as Just Eat's default "best match" sort presents them (or by sort_by, if set), not a curated subset. Each restaurant carries its unique_name (the value the restaurant and menu endpoints take), name, image, rating, delivery time window, and open-now status. A postcode with no coverage returns an empty list rather than an error.
MCP-Tool justeat_search
/justeat/restaurantReturns one Just Eat restaurant by `unique_name`, the slug found in a search result. The response has the restaurant id, name, address, city, postal code, country, image, primary cuisine, rating and rating count, and `is_active`, which says whether it currently accepts orders. `rating` can read `0` even when the site shows one. An unknown `unique_name` returns `404`.
MCP-Tool justeat_restaurant
/justeat/restaurant/menuReturns one restaurant's full menu grouped into categories. Every item carries a name, description, image, price, and calorie/energy text when the upstream provides it. Items with customization options (e.g. "Dip 1/2") carry a modifier_groups list with each option's own price. Non-restaurant stores (groceries, alcohol, pharmacy, electronics, and similar) return every item under a single "All items" category rather than the site's own finer-grained grouping.
MCP-Tool justeat_restaurant_menu
/justeat/search/filtersReturns the exact filter slugs Just Eat's own area page currently offers for a UK postcode -- star-rating thresholds, boolean toggles (open_now, new, free_delivery, halal, vegan, ...), cuisine tiles (pizza, chinese, italian, ...), and non-restaurant top-nav verticals (groceries, alcohol, pharmacy, electronics, flowers, gifts, and more) alike -- each with the live count of restaurants it currently narrows this postcode's listing to. Every filter value is the literal string /justeat/search's repeatable filter parameter accepts. The slug set is genuinely postcode-dependent: a rural postcode's own area page offers fewer cuisine tiles than central London's, because Just Eat's own frontend never advertises a filter with zero local coverage -- call this endpoint again for a different postcode rather than assume one location's slug set applies everywhere.
MCP-Tool justeat_search_filters
Verwandte APIs
Marketplaces & Retail
Separate an auction that is still open from a completed sale, and use BaT's own make and model directory to carry valid IDs into search and price-history requests.
Marketplaces & Retail
Treat Glovo as a local marketplace: discover the supported city first, then follow that city's category, store, menu, and collection identifiers through the catalog.
Marketplaces & Retail
Use PetSmart's hierarchical paths to scope product searches, then keep product SKU, price range, online availability, pickup eligibility, and store inventory as separate fields.
So scrapst du Just Eat
Crawlora's Just Eat endpoints return normalized public Just Eat UK marketplace data as JSON with one API key — no Just Eat account required. A pull on 2026-10-27 for the UK postcode EC1A 1BB reported 2,051 restaurants and returned 20, including one whose own postcode was different.
Pass a postcode to /justeat/search for every restaurant the site's own area page carries, ordered by Just Eat's default "best match" sort (or by sort_by) — not a curated subset. Each result carries its unique_name, name, image, rating, delivery time window, and open-now status.
Pass a unique_name from /justeat/search to /justeat/restaurant for its name, address, primary cuisine, rating, and whether it currently accepts orders.
Call /justeat/restaurant/menu for the full menu grouped into categories, with price and calorie/energy text where published. Non-restaurant stores (groceries, alcohol, pharmacy, electronics) return every item under a single "All items" category rather than the site's finer-grained grouping.
search returned total_count 2,051 and 20 restaurants. The first, Amison Kiosk, had unique_name amison-kiosk-london, a 5.0 rating from 246 ratings and a minimum ETA of 15 minutes.
That first row's own postal_code was EC4Y 1DH, not the searched EC1A 1BB, so results are restaurants that deliver to the area. Keep the search postcode with every row.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft Just Eat-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken Just Eat ab:
Researches restaurants and grocery/food delivery via the Crawlora API — Yelp reviews, OpenTable reservations, DoorDash and Uber Eats restaurant…
npx skills add github.com/Crawlora-org/crawlora-skills --skill restaurant-food-delivery-researchFAQ
Call /justeat/search with a UK postcode for the full restaurant listing, /justeat/restaurant for one restaurant's detail, or /justeat/restaurant/menu for its priced menu — all return structured JSON with one API key.
A full listing — every restaurant the site's own postcode area page carries, in Just Eat's default "best match" order or your chosen sort_by, not a curated feed.
Yes — /justeat/restaurant/menu works for groceries, alcohol, pharmacy, electronics, and similar stores too, though these return every item under one "All items" category rather than the site's own finer-grained grouping.
/justeat/search returns an empty list rather than an error for a postcode with no coverage.
No. The first row for EC1A 1BB on 2026-10-27 had postcode EC4Y 1DH, because it is a delivery area.