Restaurant locator and footprint mapping
Use Burger King endpoints to turn restaurant locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Turn Burger King's public restaurant and ordering data into structured JSON — restaurant locations with per-channel amenity flags, live per-channel open/closed status, restaurant-specific priced menus, and full item and combo customization trees. Credential-free.
Find Burger King restaurants, get real-time fulfillment status, and pull full priced menus with customization detail as structured JSON.
Endpoint families
4
Documented params
19
Examples
4
Live catalog snapshot
Active endpoints
4
Methods
GET
Required params
10
Schema refs
4
{
"platform": "Burger King",
"endpoint": "burgerking-locations",
"method": "GET",
"path": "/burgerking/locations",
"auth": "apiKey"
}Use cases
Find Burger King restaurants, get real-time fulfillment status, and pull full priced menus with customization detail as structured JSON.
Use Burger King endpoints to turn restaurant locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Use Burger King endpoints to turn restaurant-specific price monitoring into repeatable API requests with documented inputs and JSON responses.
Use Burger King endpoints to turn real-time fulfillment and delivery-zone research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Burger King endpoint catalog — 4 endpoints, 19 documented request parameters, and 4 published response schemas — the same catalog Docs and Playground run against.
4 documented Burger King endpoints, grouped into 4 request families — Availability, Locations and Menu, plus 1 more.
19 request parameters are documented across those Burger King endpoints, 10 of them required — the full input contract is public before you write any integration code.
4 of the 4 Burger King endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Burger King 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 Burger King endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/burgerking/availability
/burgerking/locations
/burgerking/menu
/burgerking/product
Endpoint catalog
/burgerking/locationsReturns Burger King restaurants near a latitude/longitude. Each restaurant carries its internal id and numeric store id (the value /burgerking/menu and /burgerking/availability take), full address with coordinates, phone, the operating franchise group, amenity flags (breakfast, delivery, drive-thru, playground, takeout, wifi, halal, dark kitchen) and the full published week of hours for dining room, drive-thru, delivery and curbside separately. A coordinate with no nearby Burger King returns an empty list rather than an error. Setting include_availability=true additionally returns each restaurant's live per-channel open/closed status in one call, the same shape /burgerking/availability returns -- note that path is capped at a fixed page (up to 20 restaurants) rather than honoring max_results beyond that. Setting delivery_only=true instead restricts results to restaurants that Burger King's own delivery service actually considers deliverable to this coordinate -- a genuine delivery-zone match, not the same set as filtering has_delivery=true. include_availability and delivery_only cannot be combined.
MCP tool burgerking_locations
/burgerking/availabilityReturns one restaurant's live open/closed status per order channel (curbside, delivery, drive-thru, eat-in, mobile-order drive-thru, takeout), distinct from /burgerking/locations' published weekly schedule. Each channel carries whether it is taking orders right now, its current open window when open, and the following window's start/end -- a channel with no current or next window at all means this restaurant does not offer it, not merely that it is closed. Also returns the restaurant's own local time, timezone and an overall available flag. Setting forecast=true additionally returns a multi-day forward schedule per channel, including two catering-only channels not present in the current-status list.
MCP tool burgerking_availability
/burgerking/menuReturns one restaurant's full menu grouped into categories (e.g. "Breakfast Sandwiches", "Flame Grilled Burgers"). Every entry is an item, a combo, or a picker (a variant-choice product such as "choose your drink size") and carries a delivery and pickup price -- these genuinely differ -- plus calories, detailed nutrition facts and flagged allergens when Burger King publishes them, and an image. Prices and availability reflect this specific restaurant, not a national default.
MCP tool burgerking_menu
/burgerking/productReturns one menu entry's full detail (name, description, price, image, nutrition, allergens) plus its customization tree, when it has one -- a combo's courses and their swappable entree/side/drink choices, a picker's size/variant choices, or a customizable item's ingredient toggle groups (e.g. "Bacon": no/regular/extra) and their price deltas. Options recurses through the full upstream structure, so a combo's entree choice carries its own ingredient toggles too, not just the combo's own top-level courses. A plain, non-customizable item returns an empty options list.
MCP tool burgerking_product
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
How to scrape Burger King
Crawlora's Burger King endpoints return normalized public Burger King data as JSON with one API key — no Burger King account required. Prices and availability reflect one specific restaurant, not a national default.
Pass a latitude and longitude to /burgerking/locations for nearby restaurants with amenity flags (breakfast, drive-thru, halal, dark kitchen) and full weekly hours per channel. Set delivery_only=true to restrict results to restaurants Burger King's own delivery service actually considers deliverable to that coordinate — a genuine delivery-zone match, not the same set as filtering has_delivery=true.
Call /burgerking/availability with a store_id for live open/closed status per channel (curbside, delivery, drive-thru, eat-in, mobile-order drive-thru, takeout) — a channel with no current or next window means this restaurant doesn't offer it at all, not merely that it's closed right now. Set forecast=true for a multi-day forward schedule.
Call /burgerking/menu with a store_id for that restaurant's full menu grouped into categories, with delivery and pickup prices that genuinely differ, plus calories, nutrition, and allergens where published.
Pass a store_id and item_id to /burgerking/product for a combo's swappable entree/side/drink choices, a picker's size/variant options, or a customizable item's ingredient toggles — options recurses through the full structure, so a combo's entree choice carries its own toggles too.
FAQ
Call /burgerking/locations with a coordinate for nearby restaurants, /burgerking/availability for live per-channel fulfillment status, /burgerking/menu for a restaurant's priced menu, or /burgerking/product for full item customization detail — all return structured JSON with one API key.
Yes — /burgerking/menu and /burgerking/product return delivery and pickup prices for one specific restaurant, not a national default, and the two prices genuinely differ from each other.
Yes — pass delivery_only=true to /burgerking/locations to restrict results to restaurants whose real delivery zone actually covers that coordinate, not just restaurants flagged as offering delivery in general.
It means that restaurant doesn't offer that fulfillment channel at all — not that the channel is temporarily closed. A channel that's genuinely just closed right now still reports its next opening window.