Browse the full Starbucks menu API

Endpoint facts

Method

GET

API path

/starbucks/menu

Auth

apiKey

Credits

1 credit/request

Platform

Starbucks

Response schema

#/definitions/starbucks.menuResponseDoc

Overview

Returns Starbucks' full menu as a category tree: top-level categories, their child categories, and every product with its product number, form, product type, sizes, default size, availability, and image. Pair a product's product_number and form with /starbucks/product to fetch full detail including nutrition. store_number optionally scopes the menu to one store, using a store number from /starbucks/stores; a store-scoped menu marks items that store does not carry with availability NotAvailableHere, while the unscoped menu reports everything as Available. market selects which country catalog to return, one of us or ca, defaulting to us; the two differ substantially (roughly 282 US products vs 253 CA, with exclusives on both sides). Only these two markets are available: every other Starbucks country site runs a different platform, and the European ones disallow API access in robots.txt. 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

- Categories nest via `children`; products hang off the category that lists them. A category holds either child categories or products, not usually both. - Each product carries `product_number` and `form`. Pair those two with `/starbucks/product/{product_number}/{form}` to fetch full detail including nutrition. `product_detail_url` is the matching page on starbucks.com. - `form` is the normalized lowercase form slug: `hot`, `iced`, `single`, `packaged`, `whole-bean`, or `via`. - `product_type` is Starbucks' own coarse classification in the menu tree: `Beverage`, `Food`, or `Coffee`. - `availability` is `Available` for every product on the unscoped menu. When `store_number` is given, items that store does not carry are marked `NotAvailableHere`, so a store-scoped menu is the only way to get real per-store availability. - This menu is Starbucks' **US catalog and is not localized** — there is no locale parameter, and the upstream ignores language negotiation. (The store locator, by contrast, genuinely is worldwide.) - No prices. Starbucks does not expose dollar pricing on this surface. - `category_count` counts top-level categories; `product_count` counts distinct products anywhere in the tree. Example response: ```json { "code": 200, "msg": "OK", "data": { "store_number": "101-54", "category_count": 9, "product_count": 265, "source_url": "https://www.starbucks.com/apiproxy/v1/ordering/menu?storeNumber=101-54", "fetched_at": "2026-08-30T10:31:08Z", "categories": [ { "name": "The Latest", "display_order": 1, "children": [ { "name": "Trending", "display_order": 1, "products": [ { "name": "Iced Pumpkin Cream Chai", "product_number": "2123774", "form": "iced", "product_type": "Beverage", "availability": "Available", "image_url": "https://cloudassets.starbucks.com/is/image/sbuxcorp/IcedPumpkinCreamChaiTeaLatte", "display_order": 1, "sizes": ["Tall", "Grande", "Venti"], "default_size": "Grande", "default_size_sku": "11151107", "menu_uri": "/product/2123774/iced", "product_detail_url": "https://www.starbucks.com/menu/product/2123774/iced" } ] } ] } ] } } ```

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