Store locator and footprint mapping
Mit Shake Shack-Endpunkten verwandelst du store locator and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Shake Shack's public store and menu data into structured JSON — the full store index parsed from the site's own map and text-list sections, coordinate-based nearby search against the live ordering API with real-time fulfillment-mode availability, per-store detail (address, coordinates, phone, hours, order types), and each location's full menu with customization trees and calorie deltas. Credential-free.
Browse Shake Shack's store index, find nearby locations with live ordering status, and get full store and menu detail as structured JSON.
Endpunkt-Familien
4
Dokumentierte Parameter
12
Beispiele
4
Live-Katalog-Snapshot
Aktive Endpunkte
4
Methoden
GET
Pflichtparameter
8
Schema-Referenzen
4
{
"platform": "Shake Shack",
"endpoint": "shakeshack-locations",
"method": "GET",
"path": "/shakeshack/locations",
"auth": "apiKey"
}Use Cases
Browse Shake Shack's store index, find nearby locations with live ordering status, and get full store and menu detail as structured JSON.
Mit Shake Shack-Endpunkten verwandelst du store locator and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Shake Shack-Endpunkten verwandelst du order-type and service-coverage research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Shake Shack-Endpunkten verwandelst du menu and customization monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Shake Shack-Endpunkten verwandelst du local retail presence monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Shake Shack-Endpunktkatalog — 4 Endpunkte, 12 dokumentierte Request-Parameter und 4 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
4 documented Shake Shack endpoints, grouped into 4 request families — Locations, Menu and Nearby, plus 1 more.
12 request parameters are documented across those Shake Shack endpoints, 8 of them required — the full input contract is public before you write any integration code.
4 of the 4 Shake Shack endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Shake Shack endpoints document their error responses (400, 404, 429 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 Shake Shack endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/shakeshack/locations
/shakeshack/menu
/shakeshack/nearby
/shakeshack/store
Endpunktkatalog
/shakeshack/locationsReturns one page of Shake Shack's store index, parsed off the single, fully server-rendered /locations page. That page carries two independent sections: an interactive map (coordinates, no structured address) and an accessible "Full List of Locations" text index (structured address, no coordinates). Each entry's source field says which section it came from -- "map" or "list" -- not a business classification; both round-trip through GET /shakeshack/store by path, which always returns full structured address and coordinates regardless of source.
MCP-Tool shakeshack_locations
/shakeshack/nearbyReturns Shake Shack locations within a radius of a coordinate, nearest first, using Shake Shack's own Olo-backed ordering API (a separate source from GET /shakeshack/locations, which reads the main site's store directory instead). Each result carries location_id, real-time weekly hours, which fulfillment modes are currently enabled (dine-in, pickup, delivery, curbside, drive-thru, walk-up, drive-up), and Shake Shack's own delivery fee schedule. Pass location_id to GET /shakeshack/menu for that location's full menu.
MCP-Tool shakeshack_nearby
/shakeshack/storeReturns one Shake Shack store: postal address, coordinates, phone (when published), a Monday-first week of opening hours (omitted for a location that publishes no schedule, seen on venue/kiosk-shaped locations such as inside a stadium), and the order types Shake Shack publishes for it, e.g. "Dine In", "Delivery". Store paths come from GET /shakeshack/locations, either the aliased "location/<slug>" form or the legacy "node/<id>" form -- both resolve to the same record, and the response's own path field always reports the canonical alias. A path with neither shape, or one that does not resolve to a real store page, returns a 404.
MCP-Tool shakeshack_store
/shakeshack/menuReturns one Shake Shack location's full menu as a category tree: every category and its products, with name, description, base calories, allergens, a promotional/dietary badge when published (e.g. "LIMITED TIME ONLY", "VEGETARIAN"), image, and a full customization tree (size, additions, removals, allergen flags), each choice carrying its own price and calorie delta. location_id comes from GET /shakeshack/nearby. Many items, most notably burgers, price entirely through a required size selection rather than a base price, so price is commonly 0 for those items -- the real price lives on the size modifier's own choices.
MCP-Tool shakeshack_menu
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 Shake Shack
Crawlora's Shake Shack endpoints return normalized public Shake Shack store and menu data as JSON with one API key — no Shake Shack account required.
Call /shakeshack/locations, paginated with page and page_size, for entries parsed off the site's single /locations page — its map section (coordinates, no structured address) and its accessible "Full List of Locations" text index (structured address, no coordinates). Each entry's source field says which section it came from; both round-trip through /shakeshack/store to the same full record.
Pass a latitude, longitude, and optional radius/limit to /shakeshack/nearby for the closest locations, nearest first, sourced from Shake Shack's own Olo-backed ordering API rather than the main-site directory — each result carries location_id, real-time weekly hours, and which fulfillment modes (dine-in, pickup, delivery, curbside, drive-thru, walk-up) are currently enabled.
Pass a path from /shakeshack/locations to /shakeshack/store for that location's postal address, coordinates, phone (when published), a Monday-first week of hours, and its published order types — hours are omitted for venue/kiosk-shaped locations (e.g. inside a stadium) that publish no schedule.
Store paths come in an aliased "location/<slug>" form or a legacy "node/<id>" form — both resolve to the same store record, and /shakeshack/store's response always reports the canonical alias in its own path field regardless of which form you passed.
Pass the location_id from /shakeshack/nearby to /shakeshack/menu for that location's complete category tree — every product with name, description, base calories, allergens, a promotional/dietary badge when published (e.g. "LIMITED TIME ONLY", "VEGETARIAN"), image, and a full customization tree (size, additions, removals, allergen flags) where each choice carries its own price and calorie delta.
On 2026-10-30 /shakeshack/locations reported total 529 over 14 pages of 40, nearby for midtown Manhattan returned 10 locations within 15 miles, and the menu for location 14992 held 12 categories and 81 products.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft Shake Shack-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken Shake Shack 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 /shakeshack/locations to browse the store index or /shakeshack/nearby with a coordinate for the closest locations, pass a path to /shakeshack/store for full store detail, or a location_id to /shakeshack/menu for that location's menu — all return structured JSON with one API key.
/shakeshack/locations parses two independent sections of the site's own /locations page — an interactive map (coordinates only) and a text list (structured address only) — and reports which one a given entry came from via source. Calling /shakeshack/store for that same location always returns both, regardless of source.
No — venue/kiosk-shaped locations, such as one inside a stadium, can publish no schedule at all; /shakeshack/store omits hours for those rather than fabricating a week.
Whatever Shake Shack itself publishes for that specific store, e.g. "Dine In" or "Delivery" — not a fixed list, since availability varies by location.
/shakeshack/locations parses the main site's static store-directory page. /shakeshack/nearby is a separate, coordinate-based lookup against Shake Shack's own Olo-backed ordering API, returning real-time weekly hours and which fulfillment modes are currently enabled — live ordering status the directory page doesn't carry.
Yes — /shakeshack/menu returns each product's full customization tree (size, additions, removals, allergen flags), with every choice carrying its own price and calorie delta, plus base calories, allergens, and any published promotional or dietary badge.
Many items, most notably burgers, price entirely through a required size selection rather than a base price — the real price lives on that item's "Select Size" modifier group (e.g. Single, Double, Triple), not a parsing gap.