Store locator and footprint mapping
Domino'sエンドポイントを使えば、「Store locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Domino's public ordering data into structured JSON — store locator by address, city/state, or ZIP code, full store profiles with per-service-method hours and wait windows, structured menus with variant pricing, each store's active coupons, and the full build-your-own customization catalog (sizes, crusts, toppings, sides). Credential-free.
Find Domino's stores, get full structured menus with pricing, pull store coupons, and get the full build-your-own customization catalog as structured JSON.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
20
サンプル数
6
ライブカタログスナップショット
稼働エンドポイント
6
メソッド
GET
必須パラメータ
12
スキーマ参照
6
{
"platform": "Domino's",
"endpoint": "dominos-store-locator",
"method": "GET",
"path": "/dominos/store-locator",
"auth": "apiKey"
}ユースケース
Find Domino's stores, get full structured menus with pricing, pull store coupons, and get the full build-your-own customization catalog as structured JSON.
Domino'sエンドポイントを使えば、「Store locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Domino'sエンドポイントを使えば、「Menu and pricing monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Domino'sエンドポイントを使えば、「Coupon and promotion tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Domino'sエンドポイントを使えば、「Product customization and topping-pricing research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のDomino'sエンドポイントカタログから取得しています（エンドポイント6件、ドキュメント化されたリクエストパラメータ20個、公開レスポンススキーマ6件）。DocsとPlaygroundが参照しているカタログと同じものです。
Domino'sのエンドポイントは6件、6つのリクエストファミリーに分類されています（Coupons、Customization、Menuほか3件）。
これらのDomino'sエンドポイントには20個のリクエストパラメータがドキュメント化されており、うち12個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
6件のDomino'sエンドポイントのうち6件が実際のサンプルレスポンスを、6件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Domino'sのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Domino'sのエンドポイントは6個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/dominos/coupons
/dominos/customization
/dominos/menu
/dominos/nutrition
/dominos/store
/dominos/store-locator
エンドポイントカタログ
/dominos/store-locatorReturns Domino's US stores that can serve a location: store id, address with coordinates, phone, open/online status, per-service-method availability (delivery, carryout, drive-up carryout), contactless option status, Domino's own hours summary per service method, and estimated wait windows. At least one of postal_code, or both city and state, is required; address is an optional street line that improves precision when combined with city/state. The response's query field echoes how Domino's own address resolver actually interpreted the input, including its granularity (e.g. resolved to a specific street range vs. only a city/region).
MCPツール dominos_store_locator
/dominos/storeReturns one Domino's US store's full profile -- richer than /dominos/store-locator's per-store summary. Includes the store's complete weekly hours (general hours and each service method's own hours, Monday-first, with every open/close window per day), Domino's own free-text hours summary per service method, per-service-method estimated wait windows, open/online status, per-service-method order availability (delivery, carryout, drive-up carryout, dine-in), contactless option status, and delivery/carryout order minimums. Store ids come from GET /dominos/store-locator. An unknown store id returns 404.
MCPツール dominos_store
/dominos/menuReturns one Domino's US store's full menu, as a flat list of categories (each with a stable code/name path, e.g. "Pizza > Specialty Pizzas") and their items. Each item carries its code, name, description, and product type, plus every purchasable variant (size/style) with its own code, name, and price. Store ids come from GET /dominos/store-locator. An unknown store id returns 404.
MCPツール dominos_menu
/dominos/customizationReturns one Domino's US store's full build-your-own customization catalog, grouped by product category (Domino's own names, e.g. "BuildYourOwnDomino" for pizza, "GSalad" for garden salads): every selectable size, crust/flavor style, topping, and side, each with its own code, name, description, dietary/placement flags (e.g. Meat, Vege, Sauce, WholeOnly), and any other attributes Domino's attaches (e.g. ExclusiveGroup for mutually-exclusive options). Also returns cooking instructions (bake level, cut style, seasoning), grouped. Store ids come from GET /dominos/store-locator. An unknown store id returns 404.
MCPツール dominos_customization
/dominos/couponsReturns one Domino's US store's available coupons and deals: standalone coupons (code, name, description, price, valid service methods, and any alternate promo/marketing codes that resolve to the same coupon), plus tiered volume-discount coupon groups (e.g. "order 7+ pizzas, get 15% off"). Reads the same structured menu response as GET /dominos/menu, so it costs no additional upstream request. A store can genuinely have zero active coupons -- an empty list is not an error. Store ids come from GET /dominos/store-locator. An unknown store id returns 404.
MCPツール dominos_coupons
/dominos/nutritionReturns calorie information (Domino's own "Cal-O-Meter" data) for one product at one store. For a named/fixed menu item (a specialty pizza, bread, wing, pasta, sandwich, salad, drink, or dessert -- any item code from GET /dominos/menu), give only store_id and product_code; the item's default configuration is used. For a build-your-own pizza, also give size, base, and any topping codes -- calories are computed for that exact configuration, matching Domino's own live calculator. size and base must be given together; toppings requires both. Reads live, not from a cache -- each call creates and discards one anonymous cart server-side, so it is slower than this family's other endpoints. An unknown product code, or an invalid size/base/topping combination, returns an error.
MCPツール dominos_nutrition
関連API
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
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.
Domino'sのスクレイピング方法
Crawlora's Domino's endpoints return normalized public Domino's US ordering data as JSON with one API key — no Domino's account required.
Call /dominos/store-locator with a postal_code, or both city and state, to find stores that can serve that location — an optional address street line improves precision. The response's query field echoes how Domino's own resolver actually interpreted the input, including whether it matched a specific street range or only a city.
Pass a store_id to /dominos/store for its complete weekly hours (general and per-service-method), estimated wait windows, per-service-method order availability (delivery, carryout, drive-up carryout, dine-in), and delivery/carryout order minimums — richer than the locator's per-store summary.
Call /dominos/menu with a store_id for a flat category list (e.g. "Pizza > Specialty Pizzas") and every item's purchasable size/style variants, each with its own code, name, and price.
Call /dominos/customization with a store_id for every selectable size, crust/flavor style, topping, and side by product category, each with dietary/placement flags and cooking instructions — it reads the same structured menu response as /dominos/menu, so it costs no additional upstream request.
Call /dominos/coupons with a store_id for standalone coupons and tiered volume-discount groups — it also reads the same structured menu response as /dominos/menu, so it costs no additional upstream request. A store can genuinely have zero active coupons.
FAQ
Call /dominos/store-locator with a postal code or city/state to find stores, /dominos/store for a store's full profile, /dominos/menu for its structured menu with pricing, /dominos/customization for its full build-your-own catalog, or /dominos/coupons for its active deals — all return structured JSON with one API key.
No — like /dominos/coupons, it reads the same structured menu response /dominos/menu already fetches, so calling it costs no additional upstream request.
Yes — pass address alongside city and state to /dominos/store-locator for better precision, or postal_code alone. At least one of postal_code, or both city and state, is required.
No — it reads the same structured menu response /dominos/menu already fetches, so calling it costs no additional upstream request.
/dominos/menu, /dominos/store, and /dominos/coupons all return a 404 for a store id Domino's doesn't recognize — store ids should come from /dominos/store-locator.