Restaurant locator and footprint mapping
Use Popeyes endpoints to turn restaurant locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Turn Popeyes' public restaurant, menu, promotions, and loyalty data into structured JSON — restaurant locations with amenity flags and full published hours, direct store-id lookup, per-restaurant menus with real pricing where Popeyes reports it, the current catalog of named value deals and coupons, the full Popeyes Rewards loyalty catalog (bonus-points promotions, multi-step quests, and points-redemption rewards), and the published customer-support FAQ. Credential-free.
Find Popeyes restaurants, get per-restaurant menus with real pricing, pull Popeyes Rewards' loyalty catalog, and search customer FAQs as structured JSON.
Endpoint families
6
Documented params
28
Examples
8
Live catalog snapshot
Active endpoints
8
Methods
GET
Required params
12
Schema refs
8
{
"platform": "Popeyes",
"endpoint": "popeyes-locations",
"method": "GET",
"path": "/popeyes/locations",
"auth": "apiKey"
}Use cases
Find Popeyes restaurants, get per-restaurant menus with real pricing, pull Popeyes Rewards' loyalty catalog, and search customer FAQs as structured JSON.
Use Popeyes endpoints to turn restaurant locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Use Popeyes endpoints to turn menu and pricing monitoring into repeatable API requests with documented inputs and JSON responses.
Use Popeyes endpoints to turn promotion and loyalty-program tracking into repeatable API requests with documented inputs and JSON responses.
Use Popeyes endpoints to turn multi-location coverage research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Popeyes endpoint catalog — 8 endpoints, 28 documented request parameters, and 8 published response schemas — the same catalog Docs and Playground run against.
8 documented Popeyes endpoints, grouped into 8 request families — Faq, Location and Locations, plus 5 more.
28 request parameters are documented across those Popeyes endpoints, 12 of them required — the full input contract is public before you write any integration code.
8 of the 8 Popeyes endpoints ship a recorded example response, and 8 carry a documented response schema — you can code against the real JSON before the first request.
Popeyes 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.
8 hosted MCP tools back the Popeyes endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/popeyes/faq
/popeyes/location
/popeyes/locations
/popeyes/menu
/popeyes/offers
/popeyes/promotions
Endpoint catalog
/popeyes/locationsReturns Popeyes restaurants near a latitude/longitude. Each restaurant carries its internal id and numeric store id (the value /popeyes/menu takes), full address with coordinates, phone, the operating franchise group, amenity flags (breakfast, delivery, drive-thru, playground, takeout, wifi, halal, dark kitchen) and the full published week of hours for dining room, drive-thru, delivery and curbside separately. A coordinate with no nearby Popeyes returns an empty list rather than an error.
MCP tool popeyes_locations
/popeyes/locationReturns one restaurant's full detail -- the same fields /popeyes/locations returns per restaurant (address, coordinates, phone, operator, amenity flags, full published hours) -- looked up directly by its numeric store id instead of a coordinate/radius search. Useful when the store id is already known, e.g. from a prior /popeyes/locations call. An unknown store id returns a 404.
MCP tool popeyes_location
/popeyes/menuReturns one restaurant's menu grouped into categories (e.g. "Big Box", "Chicken Wraps"). Every entry is an item, a combo, a picker (a variant-choice product such as "choose your side") or a bundle, and carries a price reflecting this specific restaurant when Popeyes reports one for that exact entry -- a missing price does not mean the item is free, it means this restaurant's pricing call did not cover that entry. Some menu entries are published directly at the top level outside any named section; these are grouped into a synthetic "Featured" category (featured true).
MCP tool popeyes_menu
/popeyes/offersReturns a page of Popeyes' promotional offers/deals catalog -- named value deals (e.g. "3Pc Signature Chicken for $5"), percentage-off combos, and paper coupons. This is CMS content describing the offer catalog, the same kind of public data /popeyes/menu already reads from -- not a personalized or store-specific list, and not account/loyalty state. A missing price does not mean free; a price of 0 means the offer's discount is not expressed as a flat price (see offer_tag/name instead, e.g. a percentage-off deal). requires_authentication reflects the offer's own published redemption rules, not any account state this endpoint reads. The catalog spans hundreds of entries including ones no longer running; there is no upstream "currently active" flag, so pages should be read as reference data, not a guarantee every entry is live right now.
MCP tool popeyes_offers
/popeyes/promotionsReturns a page of Popeyes Rewards' bonus-points promotion catalog -- flat or multiplied points bonuses tied to a qualifying purchase (e.g. "Get Double Bonus Points on Your Cart, minimum $20"), distinct from /popeyes/offers (priced menu deals) and /popeyes/quests (multi-step challenges). This is public CMS content, not a signed-in member's own applied-promotions state. points_multiplier and bonus_points are mutually exclusive in practice -- a promotion is either an "Nx points" campaign or a flat bonus. start_date/end_date bound the promotion's published active window when Popeyes sets one; both empty means no published window restriction, not that the promotion is permanently active.
MCP tool popeyes_promotions
/popeyes/questsReturns a page of Popeyes Rewards' loyalty-challenge catalog -- named multi-step challenges and their reward (e.g. "Make Two Purchases, Get FREE Chicken Sandwich in the form of 550 Bonus Points"). This is public CMS content describing the challenge and its incentive, the same class of public promotional data as /popeyes/offers -- not scoped to any signed-in member and does not report which quests a given account has completed or activated. step_count is how many steps make up the quest; this build does not expose each step's own purchase-requirement rules.
MCP tool popeyes_quests
/popeyes/rewardsReturns a page of Popeyes Rewards' points-redemption catalog -- menu items and combos a member can redeem directly for a fixed number of loyalty points (e.g. "600 points for Cheese Bites"), distinct from /popeyes/offers (priced deals), /popeyes/quests (challenges) and /popeyes/promotions (bonus-points campaigns). This is public CMS content, not a signed-in member's own points balance or redemption history. points is the loyalty points cost to redeem; other per-account/per-order redemption restrictions Popeyes may publish on a reward are not exposed by this endpoint.
MCP tool popeyes_rewards
/popeyes/faqReturns a page of Popeyes' published customer-support FAQ -- questions and answers such as "How do I remove items from my cart?". This is public help-center content, not account/order-specific support state, and does not require an order id or any customer identifier.
MCP tool popeyes_faq
Related 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.
How to scrape Popeyes
Crawlora's Popeyes endpoints return normalized public Popeyes data as JSON with one API key — no Popeyes account required.
Pass a latitude and longitude to /popeyes/locations for restaurants with their internal id and numeric store id, full address and coordinates, amenity flags (breakfast, delivery, drive-thru, halal, dark kitchen), and the full published week of hours for dining room, drive-thru, delivery, and curbside separately. A coordinate with no nearby Popeyes returns an empty list rather than an error. Already have a store id? Pass it to /popeyes/location for that one restaurant's detail directly, without a coordinate search.
Pass the store id from /popeyes/locations to /popeyes/menu for that restaurant's menu grouped into categories ("Big Box", "Chicken Wraps", and more), where every entry is an item, combo, picker, or bundle.
A menu entry with no price doesn't mean the item is free — it means this restaurant's pricing call didn't cover that specific entry. Treat a missing price as unavailable data, not a zero-cost item.
Some menu entries are published directly at the top level outside any named section; /popeyes/menu groups these into a synthetic "Featured" category (featured: true) so they're not lost from the category structure.
Call /popeyes/offers, paginated with limit and offset, for Popeyes' public deals CMS content — named value deals (e.g. "3Pc Signature Chicken for $5"), percentage-off combos, and paper coupons. A missing price here doesn't mean free, the same convention as the menu endpoint.
Call /popeyes/promotions for bonus-points campaigns (e.g. double points on a qualifying purchase), /popeyes/quests for multi-step challenges and their reward, or /popeyes/rewards for the points-redemption catalog (items and combos redeemable for a fixed number of points) — all public CMS content describing the loyalty program itself, not a signed-in member's own points balance or completed-quest state.
Call /popeyes/faq, paginated with limit and offset, for Popeyes' published customer-support FAQ (US market only in this pass) — plain-text question-and-answer entries with no category field of their own upstream.
FAQ
Call /popeyes/locations with a coordinate for nearby restaurants, pass the returned store id to /popeyes/menu for that restaurant's priced menu, or /popeyes/location for one restaurant's detail directly — plus /popeyes/offers, /popeyes/promotions, /popeyes/quests, /popeyes/rewards, and /popeyes/faq for promotions, loyalty content, and support FAQs — all return structured JSON with one API key.
Prices are included when Popeyes' own pricing call covers that specific entry for that restaurant. A missing price means this restaurant's pricing data didn't cover the item, not that it's free.
Breakfast, delivery, drive-thru, playground, takeout, wifi, halal, and dark kitchen, plus the full published week of hours broken out by dining room, drive-thru, delivery, and curbside.
A synthetic category /popeyes/menu creates for menu entries Popeyes publishes outside any named section at the top level — it groups them so they still appear in the category structure, flagged featured: true.
/popeyes/offers is priced menu deals (e.g. a combo discount); /popeyes/promotions is Popeyes Rewards bonus-points campaigns; /popeyes/quests is multi-step loyalty challenges and their reward; /popeyes/rewards is the direct points-for-item redemption catalog. All four are public CMS content, not a signed-in member's own account state.
No — /popeyes/promotions, /popeyes/quests, and /popeyes/rewards describe the loyalty program's own public catalog, not any signed-in member's points balance, redemption history, or which quests they've completed or activated.
Yes — /popeyes/location takes a store_id (and optional market: US or CA) and returns that one restaurant's full detail without needing a coordinate/radius search first.