Restaurant locator and footprint mapping
Use Raising Cane's endpoints to turn restaurant locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Turn Raising Cane's public restaurant data into structured JSON — a state/city/store directory tree, coordinate proximity search with distance, full per-store detail, the complete national menu (Combos, Tailgates, Extras, Drinks), and the promotions index with each promotion's published official rules. Credential-free.
Browse Raising Cane's store directory, find restaurants by coordinate, and get store detail, the national menu, and promotion terms as JSON.
Endpoint families
6
Documented params
14
Examples
6
Live catalog snapshot
Active endpoints
6
Methods
GET
Required params
10
Schema refs
6
{
"platform": "Raising Cane's",
"endpoint": "raisingcanes-nearby",
"method": "GET",
"path": "/raisingcanes/nearby",
"auth": "apiKey"
}Use cases
Browse Raising Cane's store directory, find restaurants by coordinate, and get store detail, the national menu, and promotion terms as JSON.
Use Raising Cane's endpoints to turn restaurant locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Use Raising Cane's endpoints to turn menu and promotion monitoring into repeatable API requests with documented inputs and JSON responses.
Use Raising Cane's endpoints to turn local retail presence monitoring into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Raising Cane's endpoint catalog — 6 endpoints, 14 documented request parameters, and 6 published response schemas — the same catalog Docs and Playground run against.
6 documented Raising Cane's endpoints, grouped into 6 request families — Directory, Menu and Nearby, plus 3 more.
14 request parameters are documented across those Raising Cane's endpoints, 10 of them required — the full input contract is public before you write any integration code.
6 of the 6 Raising Cane's endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
Raising Cane'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.
6 hosted MCP tools back the Raising Cane's 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.
/raisingcanes/directory
/raisingcanes/menu
/raisingcanes/nearby
/raisingcanes/promotion
/raisingcanes/promotions
/raisingcanes/store
Endpoint catalog
/raisingcanes/nearbyReturns Raising Cane's restaurants within a radius of a latitude/longitude, ordered nearest first, each with its distance in miles and kilometres, address, coordinates, timezone, price tier and which pickup/delivery services it offers. This proximity result carries less detail than GET /raisingcanes/store (Raising Cane's own nearby-search key is not configured with hours or phone) -- each result's `path` chains straight into GET /raisingcanes/store for the full record. `total_in_radius` reports how many stores fall inside the radius overall, which is usually far more than one page; use `offset` to walk it. A coordinate with no Raising Cane's nearby returns an empty list rather than an error.
MCP tool raisingcanes_nearby
/raisingcanes/directoryReturns one level of Raising Cane's store directory tree. Omit path for the root, which lists the US states Raising Cane's operates in; pass a child's path to descend (state to cities, city to stores). Each child carries its name, path, URL and how many stores sit under that branch. A child with is_store true is a store record rather than another directory level -- pass its path to GET /raisingcanes/store. This is a directory browse, not a proximity search: use GET /raisingcanes/nearby for a radius lookup.
MCP tool raisingcanes_directory
/raisingcanes/storeReturns one Raising Cane's store: name, full postal address, phone, coordinates, its general weekly hours plus separately published dine-in and drive-thru hours, Raising Cane's own per-store amenity labels (e.g. DRIVE_THRU, CURBSIDE_PICKUP), which pickup/delivery services it offers, and its Google Place id. Store paths come from GET /raisingcanes/directory entries whose is_store is true. Passing a directory path here returns a 404 rather than a hollow record.
MCP tool raisingcanes_store
/raisingcanes/menuReturns Raising Cane's full published menu: every section (Combos, Tailgates, Extras, Drinks) and every item, each with its name, Raising Cane's own item description (commonly ending in a calorie count or range), and image. This is a single fixed national menu page, not a per-store or per-region menu -- it takes no parameters. Raising Cane's does not publish price on this page; pricing lives behind the separate order.raisingcanes.com ordering flow, which needs a selected store and is out of scope here.
MCP tool raisingcanes_menu
/raisingcanes/promotionsReturns Raising Cane's full promotions index: every current and past sweepstakes, giveaway, and other promotion the site links to, grouped under Raising Cane's own category headings (e.g. "Sweepstakes & Giveaways", "Lucky Promotions", "First Promotions"). Each entry's path chains into GET /raisingcanes/promotion for that promotion's full official-rules text. Some entries carry an empty path -- Raising Cane's own index links a since-expired promotion back to the homepage rather than removing the entry; treat an empty path as no longer resolvable rather than a bug.
MCP tool raisingcanes_promotions
/raisingcanes/promotionReturns one Raising Cane's promotion's published official terms: title and official-rules text (eligibility, prize details, effective date), exactly as the promotion's own page publishes them, as separate paragraphs in publication order. Promotion paths come from GET /raisingcanes/promotions entries. A path with no promotion at it (expired, mistyped, or the empty path some index entries carry) returns a 404.
MCP tool raisingcanes_promotion
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 Raising Cane's
Crawlora's Raising Cane's endpoints return normalized public Raising Cane's data as JSON with one API key — no Raising Cane's account required. The menu is a single national page, not per-store.
Call /raisingcanes/directory with no path for the root — the US states Raising Cane's operates in — then pass a child's path to descend state to cities to stores.
Pass a latitude and longitude to /raisingcanes/nearby for restaurants nearest first with each result's distance. This is the proximity search the directory browse can't do, since walking the tree means knowing the administrative path in advance.
Pass the path from a /raisingcanes/directory entry flagged is_store to /raisingcanes/store for that restaurant's published detail.
Call /raisingcanes/menu with no parameters for Raising Cane's full published menu — every section (Combos, Tailgates, Extras, Drinks) and every item in it. This is one fixed national marketing page, not a per-store or per-region menu.
Call /raisingcanes/promotions for the full index of current and past sweepstakes, giveaways, and other promotions, grouped under Raising Cane's own category headings, then pass a promotion path to /raisingcanes/promotion for that promotion's published official rules — eligibility, prize details, and effective date.
FAQ
Call /raisingcanes/nearby with a coordinate or /raisingcanes/directory to browse the state/city/store tree, /raisingcanes/store for one restaurant's detail, /raisingcanes/menu for the national menu, and /raisingcanes/promotions plus /raisingcanes/promotion for promotions and their terms — all return structured JSON with one API key.
No — /raisingcanes/menu returns one fixed national marketing page covering every section (Combos, Tailgates, Extras, Drinks). It takes no parameters and does not vary by store or region.
Yes — /raisingcanes/promotions lists every current and past promotion under Raising Cane's own category headings, and /raisingcanes/promotion returns one promotion's published official rules text (eligibility, prize details, effective date) exactly as its own page publishes them.
Check is_store on the entry — only those paths are valid input to /raisingcanes/store; a state or city path is a directory level, not a restaurant.