Store locator and footprint mapping
Usa los endpoints de Wendy's para convertir store locator and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Turn Wendy's public store and menu data into structured JSON — a country-to-state-to-city-to-store directory across the US and Canada, coordinate/address-based nearby search, direct restaurant lookup by store id, the national day-part menu catalog, one restaurant's own priced item list with full combo bundle prices, full item detail including every size variant, modifier, and per-component allergen for simple items or the entree/side/drink build-out for combos, complete nutrition-facts panels, and available mobile-order time slots. Credential-free.
Browse Wendy's store directory and national menu, find restaurants nearby, and get item, combo, per-store pricing, and nutrition detail as JSON.
Familias de endpoints
6
Parámetros documentados
25
Ejemplos
10
Snapshot en vivo del catálogo
Endpoints activos
10
Métodos
GET
Parámetros obligatorios
19
Referencias de esquema
10
{
"platform": "Wendy's",
"endpoint": "wendys-directory",
"method": "GET",
"path": "/wendys/directory",
"auth": "apiKey"
}Casos de uso
Browse Wendy's store directory and national menu, find restaurants nearby, and get item, combo, per-store pricing, and nutrition detail as JSON.
Usa los endpoints de Wendy's para convertir store locator and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Wendy's para convertir menu and combo-pricing monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Wendy's para convertir allergen and nutrition-adjacent research 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 Wendy's — 10 endpoints, 25 parámetros de solicitud documentados y 10 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
10 documented Wendy's endpoints, grouped into 10 request families — Categories, Directory and Item, plus 7 more.
25 request parameters are documented across those Wendy's endpoints, 19 of them required — the full input contract is public before you write any integration code.
10 of the 10 Wendy's endpoints ship a recorded example response, and 10 carry a documented response schema — you can code against the real JSON before the first request.
Wendy's 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.
10 hosted MCP tools back the Wendy's 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
/wendys/categories
/wendys/directory
/wendys/item
/wendys/menu
/wendys/nearby
/wendys/nutrition
Catálogo de endpoints
/wendys/directoryReturns one level of Wendy's store directory tree. Omit path for the root, which lists Canada and the United States; pass a child's path to descend (country to states, state to cities, city to stores -- a single-store city links directly to its store page one level early). Each child carries its name, path, URL and, at the country/state/city levels, how many stores sit under that branch. A child with is_store true is a store page rather than another directory level -- pass its path to GET /wendys/store.
Herramienta MCP wendys_directory
/wendys/nearbyReturns Wendy's stores within a radius of a search location, nearest first, via order.wendys.com's own restaurant-selector proximity search (the "Use Current Location" / "City, State, or Zipcode" flow at order.wendys.com's start-an-order screen) -- a materially richer, real-distance source than locations.wendys.com's classic-Yext locator (GET /wendys/directory, /wendys/store), which publishes no geosearch of its own. The search location is either a latitude/longitude pair or a free-text address query param (city/state, zip code, or full street address) that Wendy's own service geocodes server-side -- exactly one form is required; address takes priority if both are given. Each store carries its address, coordinates, phone, distance in miles, open/closed status, its published week of general and breakfast hours, and a few order-availability flags (breakfast, carry-out, mobile order, drive-thru, delivery, wifi) the ordering app itself uses to decide whether to offer the store for the current order type.
Herramienta MCP wendys_nearby
/wendys/storeReturns one Wendy's store: name, full postal address, phone, coordinates, the published week of general restaurant hours and, separately, drive-thru hours (Wendy's often publishes these on different schedules), which third-party delivery platforms the store's own page links to, and the restaurant id and ordering URL used to start an order there. Store paths come from GET /wendys/directory entries whose is_store is true. Passing a directory path here returns a 404 rather than a hollow record.
Herramienta MCP wendys_store
/wendys/restaurantReturns one restaurant's detail looked up by its numeric store id -- the same id GET /wendys/nearby's stores[].store_id returns -- via order.wendys.com's own restaurant-selector API, rather than a locations.wendys.com Yext locator path (see GET /wendys/store, which needs a directory path instead). Publishes richer per-store data than the Yext locator: whether each fulfillment mode (carry-out, dine-in, drive-thru) is physically offered at all (not just currently open, as GET /wendys/nearby's flags reflect), plus feature flags (wifi, mobile order/pay, Coke Freestyle, digital coupons, loyalty, gift cards) and the published week of general and breakfast hours.
Herramienta MCP wendys_restaurant
/wendys/categoriesReturns every category on Wendy's national (restaurant-agnostic) menu, grouped by which of Wendy's own top-level day-parts (Lunch/Dinner, Breakfast) it appears under -- a few categories such as Coffee and Beverages appear under both. No restaurant selection is required; this is the same catalog a signed-out visitor sees before ever picking a location. Each category's slug is what GET /wendys/menu takes.
Herramienta MCP wendys_categories
/wendys/menuReturns every item in one category of Wendy's national menu: id, name, slug, Wendy's own displayed price and calorie strings, whether it is a combo (its GET /wendys/item response returns combo_slots instead of components/variants), a limited-time-offer flag, and whether it has required customization (e.g. a salad's dressing choice). Category slugs come from GET /wendys/categories.
Herramienta MCP wendys_menu
/wendys/store-menuReturns one restaurant's own priced, offered item list -- real local pricing (including full combo bundle prices, which GET /wendys/item deliberately does not compute, since a combo's own price varies by what's chosen in each slot) and any store-specific promotional items, rather than Wendy's own generic/average national-menu listing (GET /wendys/menu, /wendys/item). A request with just a store id returns real data, no session or account required.
Herramienta MCP wendys_store_menu
/wendys/itemReturns one item's full detail. A simple item (is_combo false) returns its description, base price, calories, every size/weight variant (e.g. Small/Medium/Large fries, each with its own price and calories, with is_default marking the one Wendy's own page pre-selects), and every modifier component -- default (comes with the item), extra (a paid add-on) and required (the caller must pick one option from a named group, e.g. a salad's dressing) -- each with its own ingredient description and allergen list, since Wendy's publishes allergens per-component rather than as one whole-item field. The top-level allergens field is the union across default components and each required group's default-selected option only. A combo (is_combo true) instead returns combo_slots: its entree/side/drink composition and every product each slot can be built from, since a combo's own price and calories vary by what is chosen. A combo slot's product ids are the same items sold standalone in their own categories -- call this endpoint again on one of those for its own full component/allergen detail. Category and item slugs come from GET /wendys/categories and GET /wendys/menu.
Herramienta MCP wendys_item
/wendys/nutritionReturns one item's (or combo's) complete nutrition-facts panel -- calories, fat, cholesterol, sodium, carbohydrate, protein, vitamins and minerals -- as real numbers, plus declared allergens. A simple item's panel is for its default configuration (default bun/size, default condiments, no extras, no required-group substitutions). A combo's panel (is_combo true) is the *combined* total across every slot's default option in one request, the same way a caller building the full order would sum it themselves -- combo_selections lists which option each slot was computed for. GET /wendys/item and GET /wendys/menu only ever carry a calorie count, because that is all Wendy's own menu pages themselves publish inline; the full panel is fetched separately by Wendy's own "Nutrition" tab, and this endpoint resolves and calls that same source so a caller does not have to reverse-engineer it. A nutrient Wendy's does not publish is omitted from the response rather than reported as zero. Category and item slugs come from GET /wendys/categories and GET /wendys/menu.
Herramienta MCP wendys_nutrition
/wendys/time-slotsReturns one restaurant's available mobile-order arrival ("check-in") time slots -- the times a caller can schedule a mobile pickup order for, distinct from the restaurant's general open/close hours (GET /wendys/restaurant, /wendys/store). A request with just a store id returns real available slots, no session or account required.
Herramienta MCP wendys_time_slots
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 Wendy's
Crawlora's Wendy's endpoints return normalized public Wendy's data as JSON with one API key — no Wendy's account required. The national menu catalog needs no restaurant selection; it's the same catalog a signed-out visitor sees before picking a location.
Call /wendys/directory with no path for the root (Canada and the United States), then descend country to state to city to store — a single-store city links directly to its store page one level early. Or pass a latitude/longitude or free-text address to /wendys/nearby for stores within a radius, nearest first, computed server-side with no cookies or session needed.
Pass the path from a /wendys/directory is_store entry to /wendys/store for full address, phone, coordinates, general hours, and separately-published drive-thru hours. Or pass the numeric store_id from a /wendys/nearby result to /wendys/restaurant for richer per-store data — whether each fulfillment mode is physically offered, not just currently open, plus feature flags the directory has no equivalent of.
Call /wendys/categories for every category grouped by day-part (Lunch/Dinner, Breakfast — a few like Coffee appear under both), then /wendys/menu with a category slug for that category's items, prices, calories, and combo/limited-time-offer flags.
Pass a store_id (from /wendys/nearby or /wendys/restaurant) to /wendys/store-menu for that specific restaurant's own priced, offered item list — real local pricing and any store-specific promotional items, including full combo bundle prices, which /wendys/item deliberately does not compute since a combo's price varies by what's chosen in each slot.
Pass a category and item slug from /wendys/menu to /wendys/item. A simple item returns every size/weight variant and each modifier component (default, extra, required) with its own ingredient description and allergen list. A combo instead returns combo_slots — its entree/side/drink composition and every product each slot can be built from. Since /wendys/item and /wendys/menu only carry a calorie count, pass the same category and item slug to /wendys/nutrition for that item's or combo's complete nutrition-facts panel as real numbers, plus declared allergens.
Pass a store_id (from /wendys/nearby or /wendys/restaurant) to /wendys/time-slots for that restaurant's available mobile-order arrival ("check-in") times — live order-slot availability, distinct from the restaurant's general open/close hours.
Preguntas frecuentes
Call /wendys/directory or /wendys/nearby to find stores, /wendys/store or /wendys/restaurant for full detail, /wendys/categories and /wendys/menu for the national menu, /wendys/store-menu for one restaurant's own real prices, /wendys/item for full item or combo detail, /wendys/nutrition for a complete nutrition panel, or /wendys/time-slots for mobile-order availability — all return structured JSON with one API key.
Yes — /wendys/item returns allergens per component (default, extra, and required-group options each carry their own ingredient description and allergen list), since Wendy's publishes allergens per-component rather than as one whole-item field. The top-level allergens field is the union across default components and each required group's default-selected option only. For a complete numeric nutrition-facts panel, use /wendys/nutrition.
A simple item (is_combo false) returns its own price, calories, size variants, and modifiers. A combo (is_combo true) instead returns combo_slots — the entree/side/drink composition and every product each slot can be built from — since a combo's price and calories vary by what's chosen; call /wendys/item again on a slot's product id for that item's own full detail.
Not necessarily — /wendys/store returns general restaurant hours and drive-thru hours as two separate published schedules, since Wendy's often publishes them on different windows.
/wendys/store needs a Yext directory path from /wendys/directory. /wendys/restaurant instead takes the numeric store_id from /wendys/nearby directly, and publishes richer per-store data — whether each fulfillment mode is physically offered at all, not just currently open, plus feature flags the Yext locator has no equivalent of.
Yes — /wendys/item and /wendys/menu only ever carry a calorie count, since that's all Wendy's own menu pages publish inline. /wendys/nutrition resolves the same source Wendy's own "Nutrition" tab fetches separately, for the item's or combo's complete numeric panel plus declared allergens.
No — /wendys/time-slots reads the same available-arrival-time data Wendy's own app uses to offer scheduling, for informational use; it does not place an order or reserve a slot.
Yes — /wendys/store-menu returns that one restaurant's own priced, offered item list, including full combo bundle prices that /wendys/item does not compute. /wendys/menu and /wendys/item instead return Wendy's restaurant-agnostic national listing with average/listed prices.