Grubhub API endpoint
Use Crawlora's Grubhub Timepicker API to extract supported public Grubhub 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.
/grubhub/timepickerReturns every future delivery or pickup time slot Grubhub will accept an order for, up to 7 days ahead. This is what powers the site's own "schedule my order" picker: `/grubhub/availability` tells you whether a restaurant is orderable right now plus one "next" time, while this returns the full future slot calendar a caller would need to build an actual date-and-time picker. Slots are grouped by date and given as full timestamps carrying the restaurant's real UTC offset for that instant, so a caller never has to resolve daylight-saving transitions themselves. Requesting `location_mode=DELIVERY` returns delivery slots only; `PICKUP` returns pickup slots only -- the upstream only computes one side per call. 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 |
|---|---|---|---|---|---|
| restaurant_id | string | Yes | Grubhub restaurant id | ||
| latitude | number | Yes | Diner location latitude | ||
| longitude | number | Yes | Diner location longitude | ||
| location_mode | string | Yes | Which slot grid to return Allowed values: DELIVERY, PICKUP | ||
| days | integer | No | How many days ahead to fetch, 1-7 (default 7) | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/grubhub/timepicker?location_mode=DELIVERY" \ -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": {
"restaurant_id": "698307",
"location_mode": "DELIVERY",
"earliest_order_send_time": "2026-09-01T08:34:16.969Z",
"time_zone": "America/New_York",
"days": [
{
"date": "2026-09-01",
"times": [
"2026-09-01T10:45:00-04:00",
"2026-09-01T11:00:00-04:00",
"2026-09-01T11:15:00-04:00"
]
},
{
"date": "2026-09-02",
"times": [
"2026-09-02T00:00:00-04:00",
"2026-09-02T00:15:00-04:00"
]
}
],
"source_url": "https://api-gtm.grubhub.com/restaurants/v4/timepicker/698307?orderType=standard&locationMode=DELIVERY&location=POINT(-74.006%2040.7128)",
"fetched_at": "2026-09-01T08:34:17Z"
}
}Request schema
No body schema
Response schema
#/definitions/grubhub.timepickerResponseDoc
| 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 | grubhub.TimepickerResponse | No | ||||
| data.days | array | No | ||||
| data.days[].date | string | No | 2026-09-01 | |||
| data.days[].times | array | No | Times is every orderable slot on this date, as RFC3339 timestamps carrying the restaurant's real UTC offset for that instant -- Grubhub reports the grid in local wall-clock hours and quarter-hours, so this resolves DST rather than requiring the caller to. | |||
| data.earliest_order_send_time | string | No | EarliestOrderSendTime is the very next moment Grubhub will accept an order for this restaurant, ASAP or scheduled. | |||
| data.fetched_at | string | No | ||||
| data.location_mode | string | No | DELIVERY | |||
| data.restaurant_id | string | No | 698307 | |||
| data.source_url | string | No | ||||
| data.time_zone | string | No | America/New_York | |||
| 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/grubhub/timepicker?location_mode=DELIVERY" \
-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