Menu, pricing, and promotion monitoring
Mit Pizza Hut-Endpunkten verwandelst du menu, pricing, and promotion monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Pizza Hut's public restaurant data into structured JSON — restaurant search by city, state, postal code, name, franchise code or store number with per-channel hours, one restaurant's full priced menu grouped into categories, the build-your-own customization tree for a product variant down to per-topping weight and left/right/whole placement with each option's real price delta, the choice-builder behind a deal or combo, and a checkout-time delivery serviceability and fee estimate. Credential-free.
Search Pizza Hut restaurants, get per-store priced menus, and expand deal and topping customization trees with real price deltas as JSON.
Endpunkt-Familien
6
Dokumentierte Parameter
38
Beispiele
6
Live-Katalog-Snapshot
Aktive Endpunkte
6
Methoden
GET
Pflichtparameter
20
Schema-Referenzen
6
{
"platform": "Pizza Hut",
"endpoint": "pizzahut-menu",
"method": "GET",
"path": "/pizzahut/menu",
"auth": "apiKey"
}Use Cases
Search Pizza Hut restaurants, get per-store priced menus, and expand deal and topping customization trees with real price deltas as JSON.
Mit Pizza Hut-Endpunkten verwandelst du menu, pricing, and promotion monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Pizza Hut-Endpunkten verwandelst du restaurant locator and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Pizza Hut-Endpunkten verwandelst du delivery fee and serviceability analysis in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Pizza Hut-Endpunktkatalog — 6 Endpunkte, 38 dokumentierte Request-Parameter und 6 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
6 documented Pizza Hut endpoints, grouped into 6 request families — Bundle Choices, Delivery Estimate and Menu, plus 3 more.
38 request parameters are documented across those Pizza Hut endpoints, 20 of them required — the full input contract is public before you write any integration code.
6 of the 6 Pizza Hut endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
Pizza Hut 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.
6 hosted MCP tools back the Pizza Hut endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
Diese Karten werden aus dem aktiven Endpunktkatalog generiert, damit die Landingpage dieselbe API-Oberfläche widerspiegelt, die auch Docs und Playground nutzen.
/pizzahut/bundle-choices
/pizzahut/delivery-estimate
/pizzahut/menu
/pizzahut/modifiers
/pizzahut/store
/pizzahut/stores
Endpunktkatalog
/pizzahut/menuReturns one restaurant's full menu grouped into categories (e.g. "Pizza", "Wings", "Deals"). Every entry is a product, a bundle (a deal or combo), or a standalone priced variant -- type tells callers which -- and carries a price in USD cents plus a decimal dollar value, and an image when the upstream publishes one. A product item also lists variants: every other priced size/crust/style option beyond its default (e.g. a pizza's Personal Pan through Large Original Stuffed Crust). Prices reflect this specific restaurant and order channel, not a national default. channel selects which order channel the menu is priced for (web ordering by default); prices can genuinely differ by channel (e.g. a delivery-marketplace channel vs. web). Some restaurants also carry products with no category at all (e.g. individual dip cup flavors); these are returned separately as uncategorized_items rather than silently dropped.
MCP-Tool pizzahut_menu
/pizzahut/storesReturns Pizza Hut restaurants matching a city/state/postal code/name/franchise code/store number filter. At least one filter is required -- an unfiltered call would enumerate every US restaurant in one response, which this endpoint intentionally does not expose. Each restaurant carries its store number (the value /pizzahut/menu and /pizzahut/store take), full address with coordinates, phone, whether it currently accepts online orders, and its timezone.
MCP-Tool pizzahut_stores
/pizzahut/storeReturns one Pizza Hut restaurant's detail by its exact store number, from /pizzahut/stores, including its recurring open hours per order channel (carryout, delivery, dine-in, drive-thru, catering carryout) plus each channel's ordering constraints -- minimum/maximum order amount, whether tipping is offered, and accepted payment methods. A channel this restaurant does not offer at all is omitted from hours rather than reported as always-closed.
MCP-Tool pizzahut_store
/pizzahut/modifiersReturns one product variant's full build-your-own customization tree -- every slot (e.g. "Pizza Sauce", "Pizza Cheese", "Pizza Toppings", "Crust Finishers"), every modifier within it (a specific topping, sauce flavor, or seasoning), and every weight/placement option (e.g. Light, Regular, Extra, or a Left/Right/Whole pizza-half placement) with its own real price delta -- zero for an amount already included by default, a positive upcharge for an "extra" option. variant_code comes from /pizzahut/menu's variant_code or variants[].variant_code fields.
MCP-Tool pizzahut_modifiers
/pizzahut/bundle-choicesReturns one deal/combo's full choice-builder tree -- every named slot it offers (e.g. "1st Pizza", "Wings or Fries", "1st Dip") and every product variant a caller can pick to fill that slot, each with the real price delta selecting it adds over the bundle's base price (zero for a variant already covered by the deal, positive for an upgrade such as a larger size or a specialty pizza). This is a different structure from /pizzahut/modifiers -- that endpoint customizes toppings/sauces on one product variant, while this endpoint swaps whole product variants in and out of a multi-item combo. bundle_code comes from /pizzahut/menu's code field on a type=bundle item.
MCP-Tool pizzahut_bundle_choices
/pizzahut/delivery-estimateChecks whether a Pizza Hut restaurant's delivery integration can deliver to a given address and, when it can, the estimated delivery fee (broken down by fee line item) and pickup/dropoff time. This reads the same checkout-time estimate Pizza Hut's own site calls -- it does not add an item to a cart or place an order, and takes no payment or account information. serviceable is true only when the upstream returned a real estimate; a false value with reason populated covers every other case seen live, such as the requested delivery_provider not being enabled at that store. For the default INTERNAL provider, a serviceable result does not by itself confirm the address is within a real deliverable radius -- see this endpoint's markdown doc for the caveat. order_subtotal materially affects the fee estimate, so it is required rather than defaulted. pickup_at defaults to 30 minutes from now (an "order now" style estimate) when omitted.
MCP-Tool pizzahut_delivery_estimate
Verwandte 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.
So scrapst du Pizza Hut
Crawlora's Pizza Hut endpoints return normalized public Pizza Hut data as JSON with one API key — no Pizza Hut account required. Menus and deals are genuinely per-restaurant, so the store number a search returns is the key to everything priced.
The stores endpoint searches by city, state, postal code, name, franchise code, or exact store number, with optional restrictions to customer-facing restaurants or those currently accepting online orders and a choice of sort orders. At least one filter is required — an unfiltered call would enumerate every US restaurant in one response, which the endpoint intentionally does not expose. Pass an exact store number to the store endpoint for one restaurant on its own, including its recurring hours per order channel.
Pass a store number to the menu endpoint for that restaurant's full menu grouped into its real categories — Pizza, Wings, Deals, Melts, Pasta, Desserts and the rest. This is store-scoped pricing, not a national reference list, so two restaurants can return different prices for the same item.
The modifiers endpoint returns one product variant's complete build-your-own tree: every slot such as Pizza Sauce, Pizza Cheese, Pizza Toppings or Crust Finishers, every modifier within it, and every weight or placement option — Light, Regular, Extra, or a left/right/whole pizza-half placement — each with its own real price delta. A delta of zero means the amount is already included by default; a positive value is a genuine upcharge.
The bundle-choices endpoint is a different structure from modifiers: where modifiers customizes toppings on one product, this returns a deal or combo's named slots — 1st Pizza, Wings or Fries, 1st Dip — and every product variant that can fill each slot, with the price delta selecting it adds over the bundle's base price. Zero for a variant the deal already covers, positive for an upgrade such as a larger size or a specialty pizza.
The delivery-estimate endpoint checks whether a restaurant's delivery integration can reach a given address and, when it can, returns the estimated fee broken down by line item plus pickup and dropoff times. It reads the same checkout-time estimate Pizza Hut's own site calls — it does not add anything to a cart, place an order, or take payment or account information.
FAQ
Search restaurants by city, state, postal code, name, franchise code or store number, then pass a store number to the menu endpoint for that restaurant's priced menu, and expand any product or deal through the modifiers and bundle-choices endpoints — all return structured JSON with one API key.
Per-store. The menu endpoint is scoped to one restaurant's store number and returns that restaurant's own prices grouped into its real categories, so two locations can list different prices for the same item. There is no national priceless reference catalog in this family — a store number is required.
No, deliberately. The stores endpoint requires at least one of store number, city, state, postal code, name, or franchise code, because an unfiltered call would return every US restaurant in a single response — a shape the endpoint intentionally does not expose. Iterate by state or postal code instead.
They customize different things. Modifiers returns one product variant's topping, sauce and seasoning tree with weight and left/right/whole placement options. Bundle-choices returns a deal or combo's slot structure — which named slots it offers and which product variants can fill each — with the price delta each choice adds over the bundle's base price.
No. It reads the same serviceability and fee estimate Pizza Hut's own site requests at checkout time: whether the restaurant's delivery integration covers the address, the estimated fee broken out by line item, and pickup and dropoff times. Nothing is added to a cart, no order is placed, and it takes no payment or account information.