Nearby Starbucks Stores API

Endpoint facts

Method

GET

API path

/starbucks/stores

Auth

apiKey

Credits

1 credit/request

Platform

Starbucks

Response schema

#/definitions/starbucks.storesResponseDoc

Overview

Returns Starbucks store locations near a point: store number, name, phone, full address, coordinates, weekly opening hours, amenities, and pick-up options. Either place, or both lat and lng, is required. place is free-text (city, address, or postal code) and is geocoded by Starbucks itself, so it works worldwide. market selects which Starbucks country site answers, one of us or ca, defaulting to us; this is not cosmetic even for stores, because the same store reports different operational data depending on the host. There is no filter parameter: Starbucks' own API accepts a features amenity filter but silently ignores it, so it is deliberately not offered here; filter on each store's returned amenities instead. A place Starbucks cannot resolve returns a well-formed empty result with place_not_found set to true rather than an error. The upstream returns at most 50 stores per request and supports no pagination; result_capped is true when that ceiling was reached. Store discovery works worldwide, but hours, amenities, and phone numbers are populated per market and may be absent outside the US and UK. 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.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- Works worldwide. `place` is geocoded by Starbucks, so cities outside the US resolve normally — confirmed against Seattle, London, Tokyo, Paris, München, São Paulo, Dubai, and Sydney. Postal codes usually work (`98104`, `10001`, `SW1A 1AA`), but Starbucks' geocoder does not resolve every one of them (`90210` does not); a failure is reported as `place_not_found`, never as an error. - The upstream returns at most **50 stores per request and supports no pagination**. `result_capped` is `true` when that ceiling was reached, meaning more stores may exist nearby that cannot be retrieved. Query around different coordinates for wider coverage. - **Three distinct outcomes, none of them errors.** Stores found (`count > 0`); a `place` that could not be geocoded (`place_not_found: true`, `count: 0`); and a `place` that geocoded fine but has no Starbucks nearby (`place_not_found: false`, `count: 0`, e.g. Utqiagvik, Alaska). The same distinction applies to a remote `lat`/`lng`. - Each store lists its `amenities` with Starbucks' own codes: `16` (In Store), `AS` (MOP ASAP + Scheduled Ordering), `BE` (Blonde Espresso), `CC` (Scanless Order and Pay), `CS` (Café Seating), `DR` (Redeem Rewards), `DT` (Drive-Thru), `EM` (Starbucks Evenings), `GO` (Starbucks Wi-Fi), `NB` (Nitro Cold Brew), `OS` (Outdoor Seating), `WA` (Oven-warmed Food), `WF` (Wireless Hot-Spot), `XO` (Mobile Order and Pay). - **Field coverage varies by market.** Store number, name, address, and coordinates are returned everywhere, but `schedule`, `amenities`, and `phone` are populated per market. Measured across all 50 results per market: United States 50/50 have a weekly schedule, amenities and phone; United Kingdom 49/50; France 47/50 have a schedule but no amenities and no phone; Japan 0/50 have a schedule, amenities, or phone, and every store reports `hours_status` of "Store hours aren't available". Do not read an empty `schedule` as a closed store. - `store_number` is Starbucks' own public store identifier and is what `/starbucks/menu` and `/starbucks/product` accept as `store_number`. - `ownership_type_code` distinguishes company-operated (`CO`) stores from licensed ones such as airport and grocery kiosks. - `mobile_ordering_availability` is a live readiness state (e.g. `READY`, `NOT_READY`), not a static capability — a store that supports mobile ordering still reports `NOT_READY` while closed. Use the `XO` amenity code for the static capability. - `distance_miles` is the distance from the searched point. Example response: ```json { "code": 200, "msg": "OK", "data": { "place": "Seattle, WA", "place_not_found": false, "result_capped": true, "count": 50, "source_url": "https://www.starbucks.com/apiproxy/v1/locations?place=Seattle%2C+WA", "fetched_at": "2026-08-30T10:31:02Z", "stores": [ { "store_number": "101-54", "id": "11311", "name": "Columbia Center - 4th & Cherry", "phone": "+1 206-447-9934", "distance_miles": 0.1639, "address": "701 Fifth Ave", "city": "Seattle", "state": "WA", "postal_code": "98104", "country": "US", "latitude": 47.60422, "longitude": -122.33078, "time_zone": "GMT-07:00 America/Los_Angeles", "ownership_type_code": "CO", "open": false, "is_open_24_hours": false, "hours_status": "Closed today", "mobile_ordering_availability": "NOT_READY", "guest_ordering": true, "amenities": [ { "code": "16", "name": "In Store" }, { "code": "XO", "name": "Mobile Order and Pay" } ], "pick_up_options": [ { "code": "16", "name": "In store", "available": false } ], "schedule": [ { "day_of_week": "SUNDAY", "hours": "Closed", "open": false }, { "day_of_week": "MONDAY", "hours": "5:00 AM to 6:00 PM", "open": true } ] } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related