Store locator and footprint mapping
Usa los endpoints de Wingstop para convertir store locator and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Turn Wingstop's public store and menu data into structured JSON — a directory browse from country to state to city to store, coordinate-based nearby search, delivery-address-to-store resolution, full per-store detail including general weekly hours plus a per-channel breakdown (pickup, delivery, takeout, drive-through), each store's full priced menu for carryout or delivery, and the complete sauce and dry-rub flavor catalog. Credential-free.
Browse Wingstop's store directory, find stores by coordinate or address, and pull each store's full detail, priced menu, and flavor catalog as JSON.
Familias de endpoints
6
Parámetros documentados
20
Ejemplos
6
Snapshot en vivo del catálogo
Endpoints activos
6
Métodos
GET
Parámetros obligatorios
16
Referencias de esquema
6
{
"platform": "Wingstop",
"endpoint": "wingstop-directory",
"method": "GET",
"path": "/wingstop/directory",
"auth": "apiKey"
}Casos de uso
Browse Wingstop's store directory, find stores by coordinate or address, and pull each store's full detail, priced menu, and flavor catalog as JSON.
Usa los endpoints de Wingstop para convertir store locator and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Wingstop para convertir delivery/pickup channel coverage research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Wingstop para convertir menu and pricing monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Wingstop para convertir local retail presence monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Wingstop — 6 endpoints, 20 parámetros de solicitud documentados y 6 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
6 documented Wingstop endpoints, grouped into 6 request families — Delivery Store, Directory and Flavors, plus 3 more.
20 request parameters are documented across those Wingstop endpoints, 16 of them required — the full input contract is public before you write any integration code.
6 of the 6 Wingstop endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
Wingstop 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 Wingstop endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
/wingstop/delivery-store
/wingstop/directory
/wingstop/flavors
/wingstop/menu
/wingstop/nearby
/wingstop/store
Catálogo de endpoints
/wingstop/directoryReturns one level of Wingstop's store directory tree. Omit path for the root, which lists the single US country node; descend country to states, states to cities, cities to stores. Each child carries its name, path, url and kind (country, state, city, or store). A child with is_store true (kind store) is a store record rather than another directory level -- pass its path to GET /wingstop/store.
Herramienta MCP wingstop_directory
/wingstop/nearbyReturns Wingstop stores within a radius of a coordinate, sorted nearest first, with enough detail per store (address, phone, general hours, fulfillment channels) that a follow-up GET /wingstop/store call is often unnecessary. Each result's slug can be passed directly as GET /wingstop/menu's path.
Herramienta MCP wingstop_nearby
/wingstop/delivery-storeGiven a delivery address, returns the single Wingstop store that will deliver there, plus its drive time. Returns 404 when no Wingstop store delivers to that address. The returned slug can be passed directly as GET /wingstop/menu's path with service_mode=delivery.
Herramienta MCP wingstop_delivery_store
/wingstop/storeReturns one Wingstop store: name, full postal address, phone, coordinates, its general weekly hours plus a per-channel breakdown (pickup, delivery, takeout, drive-through), which pickup/delivery services it offers, its operating status, price tier and Google Place id. Store paths come from GET /wingstop/directory entries whose is_store is true. Passing a directory path here returns a 404 rather than a hollow record.
Herramienta MCP wingstop_store
/wingstop/menuReturns one Wingstop store's full priced, categorized menu for carryout or delivery: every category, each listing's variants (a standalone item has one variant; a size/flavor family such as "6 pc Wing Combo" has one variant per size or preparation) with price, description and calorie range, plus store-level pricing context (currency, tax rate, prep lead time). Store paths come from GET /wingstop/directory entries whose is_store is true, or a GET /wingstop/store response's own path.
Herramienta MCP wingstop_menu
/wingstop/flavorsReturns Wingstop's full sauce and dry-rub flavor catalog: name, description, image, a 0 (no heat) to 5 (hottest) heat scale, whether it's a dry rub or wet sauce, and new/popular/limited-time badges. Includes retired flavors (is_active false) still present in Wingstop's own feed.
Herramienta MCP wingstop_flavors
APIs relacionadas
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.
Cómo hacer scraping de Wingstop
Crawlora's Wingstop endpoints return normalized public Wingstop US store data as JSON with one API key — no Wingstop account required.
Call /wingstop/directory with no path for the root (the single US country node), then descend country to states, states to cities, cities to stores. Each child carries its name, path, url, and kind (country, state, city, or store) — a child with is_store true is a store record, not another directory level.
Pass a latitude and longitude (and optional radius) to /wingstop/nearby for stores within range, nearest first — each result carries enough detail (address, phone, general hours, fulfillment channels) that a follow-up /wingstop/store call is often unnecessary, and its slug can be passed directly as /wingstop/menu's path.
Pass a delivery address (address1, city, state, postal_code) to /wingstop/delivery-store for the single Wingstop store that will deliver there, plus its drive time from that store — returns a 404 when no store delivers to the given address.
Pass the path from a directory entry flagged is_store to /wingstop/store for its name, full postal address, phone, coordinates, general weekly hours, a per-channel hours breakdown (pickup, delivery, takeout, drive-through), which pickup/delivery services it offers, operating status, price tier, and Google Place id — passing a directory path (not a store path) here returns a 404 rather than a hollow record.
Pass the store path and an optional service_mode to /wingstop/menu for every category and listing, with one variant per standalone item and one variant per size/preparation for a family like "6 pc Wing Combo" — each variant carries price, description, and calorie range. Call /wingstop/flavors (no parameters) for the full sauce/dry-rub catalog, each with a 0-5 heat_scale, is_dry, is_new, is_popular, is_limited_time, and is_active flags.
Preguntas frecuentes
Call /wingstop/directory to browse country/state/city/store levels, /wingstop/nearby for coordinate-based search, /wingstop/delivery-store to resolve a delivery address to its serving store, pass a store path to /wingstop/store for its full address, hours, channels, and status, /wingstop/menu for its priced menu, or /wingstop/flavors for the sauce/dry-rub catalog — all return structured JSON with one API key.
Yes — /wingstop/store returns general weekly hours plus a separate per-channel breakdown for pickup, delivery, takeout, and drive-through, since these can genuinely differ at the same location.
Check is_store (or kind === "store") on the entry — only those paths are valid input to /wingstop/store; a state or city path returns a 404 there instead of a hollow record.
The root currently lists a single US country node — the directory tree descends from there through US states and cities only.
One variant per size or preparation — a standalone item has a single variant, while a size/flavor family like "6 pc Wing Combo" returns one priced variant per size, each with its own description and calorie range.
Pass the address to /wingstop/delivery-store — it returns the single store that will deliver there plus its drive time from that store, or a 404 if no Wingstop store covers that address.
false marks a retired flavor Wingstop's own catalog feed still carries a record for but no longer offers or shows on its public flavors page — filter on it to see only currently-offered flavors.