Datasets API endpoint
Use Crawlora's Search the Starbucks store directory API to search or inspect stored structured datasets as JSON. This page includes request parameters, cURL examples, response schema, validation behavior, credit cost, and a Playground link for testing before integration. Dataset endpoints read indexed records and do not apply proxy routing.
/datasets/starbucks-stores/searchSearches the worldwide Starbucks store directory (dataset id `starbucks-stores`), built by grid-tiling the store locator around its 50-result cap. Each store has its store number, name, phone, full address, coordinates, weekly hours, amenity codes, and pick-up options. Store discovery is global, but hours, amenities, and phone numbers are populated per market and are largely absent outside the US, Canada, Europe, and the Gulf; an empty schedule means "not published for this market", not "closed". `country` is the store's true country while `market` is crawl provenance (the US host geocodes worldwide). Supports full-text `q`, `country`/`state`/`city`/`market`/`amenity` filters, `lat`/`lon`/`radius_m` radius filtering, and `sort` (relevance, distance_asc). Developers commonly use this endpoint for repeatable dataset search, filtering, facets, local business enrichment, analytics, exports, and internal tools that need structured records beyond the limited manual refinement available in the Google Maps app. Authentication uses the x-api-key header, usage is metered with the credit cost shown on this page, and the request does not trigger live scraping or proxy routing.
Request parameters are generated from the active endpoint catalog. Dataset parameters filter, page, facet, or locate stored structured records; they do not configure a live scraper or proxy path.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| q | string | No | Full-text search over store name, city, and address, max 256 characters | ||
| country | string | No | ISO-3166-1 alpha-2 country filter, e.g. US, GB, JP | ||
| state | string | No | State/region code filter, e.g. WA | ||
| city | string | No | Exact city filter | ||
| market | string | No | Crawl-provenance market filter. One of: us, ca Allowed values: us, ca | ||
| amenity | string | No | Amenity code filter, e.g. DT (Drive-Thru), XO (Mobile Order and Pay) | ||
| lat | number | No | Latitude for radius filtering or distance sort, requires lon | ||
| lon | number | No | Longitude for radius filtering or distance sort, requires lat | ||
| radius_m | integer | No | Radius in meters, 1 through 50000; requires lat and lon | ||
| sort | string | No | Sort enum: relevance, distance_asc Allowed values: relevance, distance_asc | ||
| page | integer | No | 1 | Page number, defaults to 1 | |
| page_size | integer | No | 20 and maxes at 100 | Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000 | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/datasets/starbucks-stores/search?q=coffee&country=us&market=us&sort=relevance&page=1" \ -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 reads stored indexed dataset records. It does not execute a live upstream Google Maps request, browser session, or proxy-routed scraping job.
- `country` is the store's true country; `market` is crawl provenance (the US host geocodes worldwide, so a Tokyo store has `country: JP`, `market: us`). - Store discovery is global, but `schedule` (hours), `amenities`, and `phone` are populated per market and are largely absent outside the US, Canada, Europe, and the Gulf. An empty `schedule` means "not published for this market", not "closed". - A not-yet-populated dataset returns an empty result (`total: 0`), not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "dataset": "starbucks-stores", "items": [ { "store_number": "101-54", "name": "Columbia Center - 4th & Cherry", "city": "Seattle", "state": "WA", "country": "US", "latitude": 47.60422, "longitude": -122.33078, "amenities": ["16", "XO", "DT"], "market": "us" } ], "page": 1, "page_size": 20, "total": 1, "sort": "" } } ```
Crawlora does not silently return invalid dataset search results when filters, pagination, coordinates, or stored record lookups cannot be satisfied.
| Status | Common failure case |
|---|---|
| 400 | Invalid input, missing required parameter, invalid enum, bad coordinate pair, or result window beyond the dataset limit |
| 404 | Requested stored dataset item is not present |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal dataset query or storage error |
When possible, Crawlora returns structured error context so your integration can adjust filters, page size, location inputs, or lookup identifiers.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 500 | Internal Server Error | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"dataset": "starbucks-stores",
"items": [
{
"store_number": "101-54",
"name": "Columbia Center - 4th & Cherry",
"city": "Seattle",
"state": "WA",
"country": "US",
"latitude": 47.60422,
"longitude": -122.33078,
"amenities": [
"16",
"XO",
"DT"
],
"market": "us"
}
],
"page": 1,
"page_size": 20,
"total": 1,
"sort": ""
}
}Request schema
No body schema
Response schema
#/definitions/datasets.starbucksStoresSearchResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | datasets.StarbucksStoreSearchResponse | No | ||||
| data.dataset | string | No | ||||
| data.items | array | No | ||||
| data.items[].address | string | No | ||||
| data.items[].amenities | array | No | ||||
| data.items[].amenity_names | array | No | ||||
| data.items[].city | string | No | ||||
| data.items[].country | string | No | ||||
| data.items[].crawled_at | string | No | ||||
| data.items[].distance_meters | number | No | ||||
| data.items[].first_seen_at | string | No | ||||
| data.items[].id | string | No | ||||
| data.items[].last_seen_at | string | No | ||||
| data.items[].latitude | number | No | ||||
| data.items[].location | unknown | No | Location is a geo_point ([lon, lat] order in the GeoPoint helper). | |||
| data.items[].longitude | number | No | ||||
| data.items[].market | string | No | Market is crawl provenance (us/ca), not geography -- see the type doc. | |||
| data.items[].mobile_ordering_availability | string | No | ||||
| data.items[].name | string | No | ||||
| data.items[].ownership_type_code | string | No | ||||
| data.items[].phone | string | No | ||||
| data.items[].pick_up_options | array | No | ||||
| data.items[].postal_code | string | No | ||||
| data.items[].run_id | string | No | ||||
| data.items[].schema_version | integer | No | ||||
| data.items[].state | string | No | ||||
| data.items[].store_id | string | No | ||||
| data.items[].store_number | string | No | ||||
| data.items[].time_zone | string | No | ||||
| data.page | integer | No | ||||
| data.page_size | integer | No | ||||
| data.sort | string | No | ||||
| data.total | integer | No | ||||
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/datasets/starbucks-stores/search?q=coffee&country=us&market=us&sort=relevance&page=1" \
-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