GET/wendys/categoriesapiKey1 credit/request
List Wendy's national menu categories
Returns 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.
Required params: None
GET/wendys/directoryapiKey1 credit/request
Browse the Wendy's store directory
Returns 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.
Required params: None
GET/wendys/itemapiKey1 credit/request
Get one Wendy's menu item's (or combo's) detail
Returns 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.
Required params: category:query, item:query
GET/wendys/menuapiKey1 credit/request
List one Wendy's menu category's items
Returns 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.
Required params: category:query
GET/wendys/storeapiKey1 credit/request
Get one Wendy's store's detail
Returns 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.
Required params: path:query
GET/wendys/nearbyapiKey1 credit/request
Find Wendy's stores near a coordinate or address
Returns 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.
Required params: None
GET/wendys/nutritionapiKey1 credit/request
Get one Wendy's menu item's full nutrition-facts panel
Returns 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.
Required params: category:query, item:query
GET/wendys/restaurantapiKey1 credit/request
Get one Wendy's restaurant's detail by store id
Returns 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.
Required params: store_id:query
GET/wendys/time-slotsapiKey1 credit/request
Get one Wendy's restaurant's available mobile-order time slots
Returns 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). Found via static analysis of Wendy's official Android app and confirmed credential-free: a cold, cookie-less request with just a store id returns real available slots, no session or account required.
Required params: store_id:query
GET/wendys/store-menuapiKey1 credit/request
Get one Wendy's restaurant's full priced/offered menu
Returns 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). Found via static analysis of Wendy's official Android app and confirmed credential-free: a cold, cookie-less request with just a store id returns real data, no session or account required.
Required params: store_id:query