Starbucks Product Detail API

Endpoint facts

Method

GET

API path

/starbucks/product/{product_number}/{form}

Auth

apiKey

Credits

1 credit/request

Platform

Starbucks

Response schema

#/definitions/starbucks.productResponseDoc

Overview

Returns one Starbucks product's full detail: name, description, product type, image, Rewards star cost, customization options, and every size with its own nutrition panel (serving size, calories, calories from fat, and per-fact values for total fat with saturated and trans fat subfacts, cholesterol, sodium, total carbohydrates, protein, and caffeine). product_number is the numeric id from a /starbucks/menu result or a product page URL. form is that product's form; allowed values are hot, iced, single, packaged, whole-bean, and via. store_number optionally scopes availability to one store. Starbucks does not expose dollar pricing on this surface, so no price is returned; star_cost is the Rewards star cost. market selects which country catalog to resolve against, one of us or ca, defaulting to us. Each size also carries its default_recipe, the standard build, which is the required starting point for the /starbucks/product/{product_number}/{form}/nutrition endpoint. An unknown product number, or a form that product is not sold in, returns not found. 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

- Each size carries a `default_recipe`: the standard build for that size, as a list of modifiers with `sku`, `name`, `form_code`, and `option_product_number`. This is the required starting point for `POST /starbucks/product/{product_number}/{form}/nutrition`, which wants the complete modifier set rather than a change-set. `form_code` describes how a modifier behaves: `one` is a pick-exactly-one slot (the milk), `qty` is a countable (espresso shots, syrup pumps), and `modifier`/`yes-no` are toggles. - **No price.** Starbucks does not expose dollar pricing on this surface — it is store- and session-scoped behind its authenticated ordering flow. `star_cost` is the Starbucks Rewards star cost and is the only price-like value available. - Each entry in `sizes` carries its own `nutrition` panel: `serving_size`, `calories`, `calories_from_fat`, and a `facts` list. Facts cover Total Fat (with Saturated Fat and Trans Fat as `subfacts`), Cholesterol, Sodium, Total Carbohydrates, Protein, and **Caffeine**. - `daily_percent_value` is Starbucks' own preformatted percentage, e.g. `"15%"`. - Nutrition values are normalized to strings because the upstream mixes numbers and strings for the same field. - `options` lists the customization categories Starbucks offers for the product, e.g. Milk, Flavors, Espresso. - `product_type` on this endpoint uses a different vocabulary from the menu tree's (`beverages` here versus `Beverage` there); treat it as an upstream label rather than a stable enum. - An unknown `product_number`, or a `form` that product is not sold in, returns a not-found error. Example response: ```json { "code": 200, "msg": "OK", "data": { "product_number": "418", "form": "hot", "name": "Pumpkin Spice Latte", "description": "Our signature Espresso Roast and steamed milk with the celebrated flavor combination of pumpkin, cinnamon, nutmeg and clove. Enjoy it topped with whipped cream and real pumpkin-pie spices.", "product_type": "beverages", "image_url": "https://cloudassets.starbucks.com/is/image/sbuxcorp/PumpkinSpiceLatteV1", "in_catalog": true, "star_cost": 200, "options": [ { "name": "Milk" }, { "name": "Flavors" } ], "sizes": [ { "size_code": "Short", "sku": "183885", "nutrition": { "serving_size": "8 fl oz", "calories": "210", "calories_from_fat": "80", "facts": [ { "name": "Total Fat", "value": "9 g", "unit_of_measure": "g", "daily_percent_value": "11%", "subfacts": [ { "name": "Saturated Fat", "value": "5 g", "unit_of_measure": "g", "daily_percent_value": "25%" }, { "name": "Trans Fat", "value": "0 g", "unit_of_measure": "g" } ] }, { "name": "Caffeine", "value": "150 mg", "unit_of_measure": "mg" } ] } } ], "source_url": "https://www.starbucks.com/apiproxy/v1/ordering/418/hot", "fetched_at": "2026-08-30T10:31:11Z" } } ```

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