Whataburger API Documentation

Use Crawlora's Whataburger API endpoints to extract supported public Whataburger data as structured JSON. This documentation covers 2 active endpoints including Browse Whataburger's store-URL index, Get one Whataburger store's detail. Developers can use these endpoints for monitoring, enrichment, research dashboards, internal data pipelines, and agent-native workflows without maintaining platform-specific scraping code. Each endpoint page documents authentication, request parameters such as path, cURL examples, response examples, response schemas, errors, credit cost, and Playground testing. Send requests to the Crawlora API with an x-api-key header, review usage and plan limits on pricing, and test safe sample requests in Playground before moving the workflow into production.

Try Browse Whataburger's store-URL index Start with endpoint docs Pricing

Quick start

Choose an endpoint, send an authenticated request with the x-api-key header, and inspect the normalized JSON response. The examples below use the public Crawlora API base URL and the same endpoint catalog used by Playground.

Base URL: https://api.crawlora.net/api/v1
Auth header: x-api-key: $CRAWLORA_API_KEY
Primary endpoint: GET /whataburger/sitemap
Credit cost: 2 credits/request

curl -X GET "https://api.crawlora.net/api/v1/whataburger/sitemap?page=1&kind=store" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Try Browse Whataburger's store-URL index in Playground API key authentication Review Crawlora pricing

Whataburger API endpoints

These endpoint cards are generated from the active Crawlora endpoint catalog, including method, path, auth mode, credit cost, parameter summary, docs, and Playground links.

GET/whataburger/sitemapapiKey2 credits/request

Browse Whataburger's store-URL index

Returns 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.

Required params: None

Browse Whataburger's store-URL index documentation Try Browse Whataburger's store-URL index in Playground

GET/whataburger/storeapiKey1 credit/request

Get one Whataburger store's detail

Returns 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 Whataburger's ordering/menu site returns no usable response for automated requests, so there is no credential-free menu source and this family is a locator only.

Required params: path:query

Get one Whataburger store's detail documentation Try Get one Whataburger store's detail in Playground

Endpoint reference table

Endpoint	API path	Method	Credits	Required params	Docs	Playground
Browse Whataburger's store-URL index	/whataburger/sitemap	GET	2 credits/request	None	View docs	Try endpoint
Get one Whataburger store's detail	/whataburger/store	GET	1 credit/request	path:query	View docs	Try endpoint

Related Crawlora API pages

Whataburger API Try the primary endpoint in Playground Browse supported platforms Crawlora API pricing Amazon API documentation eBay API documentation Shop.app API documentation Shopify API documentation

Back to docs