Whataburger API endpoint
Use Crawlora's Whataburger Store API to extract supported public Whataburger data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/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 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. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| path | string | Yes | Store path from a /whataburger/sitemap entry | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/whataburger/store" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"store_id": "1403",
"name": "Whataburger",
"address": {
"line1": "1625 TX HWY 351",
"city": "ABILENE",
"region": "TX",
"postal_code": "79601",
"country": "US"
},
"phone_number": "(325) 692-8480",
"latitude": 32.481983,
"longitude": -99.744767,
"hours": [
{
"day_of_week": "Monday",
"closed": false,
"opens": "00:00",
"closes": "23:59"
}
],
"services": [
"Curbside",
"Delivery"
],
"service_hours": {
"dine_in": [
{
"day_of_week": "Monday",
"closed": false,
"opens": "00:00",
"closes": "23:59"
}
],
"drive_thru": [
{
"day_of_week": "Monday",
"closed": false,
"opens": "00:00",
"closes": "23:59"
}
],
"curbside": [
{
"day_of_week": "Monday",
"closed": false,
"opens": "07:00",
"closes": "00:00"
}
],
"delivery": [
{
"day_of_week": "Monday",
"closed": false,
"opens": "00:00",
"closes": "23:59"
}
]
},
"timezone": "America/Chicago",
"google_place_id": "ChIJabc123",
"path": "tx/abilene/1625-tx-hwy-351.html",
"source_url": "https://locations.whataburger.com/tx/abilene/1625-tx-hwy-351.html",
"fetched_at": "2026-09-01T17:00:00Z"
}
}Request schema
No body schema
Response schema
#/definitions/whataburger.storeResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | Code is the HTTP status code or a custom code used to indicate the result of the request @example 200 | |||
| data | whataburger.StoreResponse | No | ||||
| data.address | whataburger.StoreAddress | No | ||||
| data.address.city | string | No | ABILENE | |||
| data.address.country | string | No | US | |||
| data.address.line1 | string | No | 1625 TX HWY 351 | |||
| data.address.line2 | string | No | ||||
| data.address.postal_code | string | No | 79601 | |||
| data.address.region | string | No | TX | |||
| data.fetched_at | string | No | ||||
| data.google_place_id | string | No | ||||
| data.hours | array | No | ||||
| data.hours[].closed | boolean | No | false | Closed is true when Whataburger publishes the day with no open interval. | ||
| data.hours[].closes | string | No | 23:59 | |||
| data.hours[].day_of_week | string | No | Monday | |||
| data.hours[].opens | string | No | 00:00 | |||
| data.latitude | number | No | 32.481983 | |||
| data.longitude | number | No | -99.744767 | |||
| data.name | string | No | Whataburger | |||
| data.path | string | No | Path is the canonical /whataburger/store path for this restaurant, as Whataburger's own entity data publishes it -- present even when the requested path was a Curbside or Delivery variant of the same store. | |||
| data.phone_number | string | No | (325) 692-8480 | |||
| data.service_hours | unknown | No | ServiceHours breaks the same week down per fulfillment channel -- dine-in, drive-thru, curbside and delivery windows can and do differ from each other and from Hours (dine-in) at the same store. Whataburger always publishes drive-thru and dine-in hours; curbside and delivery are omitted here when the entity carries no schedule for them (a store that does not list that service in Services). | |||
| data.services | array | No | Services are the restaurant services Whataburger publishes for this location, e.g. "Curbside", "Delivery". | |||
| data.source_url | string | No | ||||
| data.store_id | string | No | 1403 | |||
| data.timezone | string | No | America/Chicago | |||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/whataburger/store" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms