Store enumeration and footprint mapping
Mit Whataburger-Endpunkten verwandelst du store enumeration and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Whataburger's own sitemap-declared store index into structured JSON — about 3,950 URLs from a single flat sitemap, each entry typed by kind, plus full per-store detail for any store path. Credential-free.
Enumerate Whataburger's ~3,950-URL store index and get full per-store detail as structured JSON.
Endpunkt-Familien
2
Dokumentierte Parameter
6
Beispiele
2
Live-Katalog-Snapshot
Aktive Endpunkte
2
Methoden
GET
Pflichtparameter
3
Schema-Referenzen
2
{
"platform": "Whataburger",
"endpoint": "whataburger-sitemap",
"method": "GET",
"path": "/whataburger/sitemap",
"auth": "apiKey"
}Use Cases
Enumerate Whataburger's ~3,950-URL store index and get full per-store detail as structured JSON.
Mit Whataburger-Endpunkten verwandelst du store enumeration and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Whataburger-Endpunkten verwandelst du local retail presence monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Whataburger-Endpunkten verwandelst du store-count benchmarking against competitor chains in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Whataburger-Endpunktkatalog — 2 Endpunkte, 6 dokumentierte Request-Parameter und 2 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
2 documented Whataburger endpoints, grouped into 2 request families — Sitemap and Store.
6 request parameters are documented across those Whataburger endpoints, 3 of them required — the full input contract is public before you write any integration code.
2 of the 2 Whataburger endpoints ship a recorded example response, and 2 carry a documented response schema — you can code against the real JSON before the first request.
Whataburger 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.
2 hosted MCP tools back the Whataburger endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/whataburger/sitemap
/whataburger/store
Endpunktkatalog
/whataburger/sitemapReturns one page of Whataburger's sitemap-declared store index -- about 3,950 URLs at time of writing. Unlike some other store locators in this API, Whataburger publishes a single flat sitemap file rather than a sharded index. Each entry carries a kind: "store" is a restaurant's canonical detail page, "curbside" and "delivery" are separate pages Whataburger publishes for that same restaurant's curbside or delivery service, and "directory" is a state- or city-level listing page with no address of its own. Filter with kind to enumerate one page variant. A page past the end returns an empty list rather than an error, so a caller can walk to exhaustion.
MCP-Tool whataburger_sitemap
/whataburger/storeReturns one Whataburger store: postal address, coordinates, phone, published week of opening hours, the restaurant services (curbside, delivery) Whataburger lists for it, and a per-channel hours breakdown (dine-in, drive-thru, curbside, delivery) where the channel's hours genuinely differ from the store's top-level hours. Store paths come from GET /whataburger/sitemap -- a store's canonical, curbside and delivery page paths all describe the same physical restaurant and return the same address; the response's own path field always reports the canonical page. Passing a state or city directory path returns a 404 rather than a hollow record. Note there is no menu source, so this family is a locator only.
MCP-Tool whataburger_store
Verwandte APIs
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.
So scrapst du Whataburger
Crawlora's Whataburger endpoints return normalized public Whataburger store data as JSON with one API key — no Whataburger account required. Unlike Subway and Jimmy John's, Whataburger publishes a single flat sitemap rather than a sharded index.
Call /whataburger/sitemap to page through Whataburger's sitemap-declared store index — about 3,950 URLs at time of writing. Each entry carries a kind, and because Whataburger publishes one flat sitemap.xml rather than a sharded index, there is no shard parameter to walk.
Pass a store path from /whataburger/sitemap to /whataburger/store for that location's published detail.
Page through /whataburger/sitemap until the response comes back empty to know you've reached the end of the index, then resolve whichever store paths you need.
FAQ
Call /whataburger/sitemap to page through the store-URL index, then pass a store path to /whataburger/store for that location's full detail — both return structured JSON with one API key.
About 3,950 URLs at time of writing. Not every URL is a store page — each entry carries a kind, so filter on it to separate stores from other page types.
No — unlike Subway and Jimmy John's, Whataburger publishes a single flat sitemap.xml, so /whataburger/sitemap takes no shard parameter; just page through it.
Not in this first pass — this family covers the store index and per-store detail only.