Store enumeration and footprint mapping
Usa los endpoints de Whataburger para convertir store enumeration and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
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.
Familias de endpoints
2
Parámetros documentados
6
Ejemplos
2
Snapshot en vivo del catálogo
Endpoints activos
2
Métodos
GET
Parámetros obligatorios
3
Referencias de esquema
2
{
"platform": "Whataburger",
"endpoint": "whataburger-sitemap",
"method": "GET",
"path": "/whataburger/sitemap",
"auth": "apiKey"
}Casos de uso
Enumerate Whataburger's ~3,950-URL store index and get full per-store detail as structured JSON.
Usa los endpoints de Whataburger para convertir store enumeration and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Whataburger para convertir local retail presence monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Whataburger para convertir store-count benchmarking against competitor chains 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 Whataburger — 2 endpoints, 6 parámetros de solicitud documentados y 2 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
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.
Mapa de cobertura
/whataburger/sitemap
/whataburger/store
Catálogo de endpoints
/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.
Herramienta MCP 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.
Herramienta MCP whataburger_store
APIs relacionadas
Marketplaces & Retail
Separate an auction that is still open from a completed sale, and use BaT's own make and model directory to carry valid IDs into search and price-history requests.
Marketplaces & Retail
Treat Glovo as a local marketplace: discover the supported city first, then follow that city's category, store, menu, and collection identifiers through the catalog.
Marketplaces & Retail
Use PetSmart's hierarchical paths to scope product searches, then keep product SKU, price range, online availability, pickup eligibility, and store inventory as separate fields.
Cómo hacer scraping de 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. A pull on 2026-10-27 showed the sitemap route listing 3,969 entries across 794 pages at 5 per page, each with a kind, a store number and a path for the store route.
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.
/whataburger/store with a sitemap path such as 1197C.html returned store_id 1197, address, phone_number, latitude, longitude and a per-day hours list. The sitemap listed 3,971 entries over 795 pages at page_size 5 on 2026-10-30, and one store appears under several kinds (1197C curbside, 1197D delivery), so de-duplicate by store_number before counting restaurants.
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.
sitemap with page_size 5 returned total 3,969 and total_pages 794. Entries carry a kind (the first was curbside), a store_number (1197) and a path such as 1197C.html, which is the value the store route takes.
The store route needs the path from the sitemap, so crawl the sitemap first and store the kind with each entry.
Agent Skills
Instala un agent skill de Crawlora y tu agente obtiene datos de Whataburger como JSON mediante la API documentada, sin escribir un scraper. Estos skills cubren Whataburger:
Researches restaurants and grocery/food delivery via the Crawlora API — Yelp reviews, OpenTable reservations, DoorDash and Uber Eats restaurant…
npx skills add github.com/Crawlora-org/crawlora-skills --skill restaurant-food-delivery-researchPreguntas frecuentes
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.
3,969 entries on 2026-10-27. Entries have a kind, so check how multiple entries for the same store number are classified before counting restaurants.