Google Shopping reference
Every Google Shopping operation, from the registry
7 operations wired in the registry, 7 of them proven by real traffic.
Choose a Google Shopping operation
Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.
Reviews and offers
- Google Shopping deals — Discounted products for a query on Google Shopping with sale and original price, discount and store.
- Google Shopping reviews — Retrieve product reviews from Google Shopping. Reviewer details and source review IDs can be absent. Slow results return HTTP 202 with task_id and status_url; poll that URL at zero retrieval credits. The original task is charged once and terminal failures are refunded. Requested depth remains subject to available source capacity.
- Google Shopping sellers — Retrieve Google Shopping merchant offers with source-reported prices and currency. Base price and total price are separate; missing amounts remain unknown. Slow results return HTTP 202 with task_id and status_url; poll that URL at zero retrieval credits. The original task is charged once and terminal failures are refunded.
- Google Shopping store reviews — Shopper reviews of an online store as shown on Google Shopping, with rating, text, author and date.
Posts and media
- Google Shopping price history — Available historical prices by store for a Google Shopping product in the requested country. Current offer prices and store URLs may be absent; use google_shopping/sellers for current offers. Returns available histories in one response; coverage varies by product and country.
Products and categories
- Google Shopping product — One Google Shopping product with its description, images, specification and rating. Queued task.
Search and discovery
- Google Shopping search — Products for a query on Google Shopping with seller, price, currency and rating. Prepared as a queued task; a retry within fifteen minutes picks up the same result.
Check fields and collection limits
Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.
Agents can use get_endpoint for the current contract and get_docs with topic platforms/google_shopping to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.
Operations
Google Shopping
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Google Shopping
7 operationsElsewhere
The same registry, other shapes
- Google Shopping overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=google_shopping— the same rows to your code at runtime, for 0 credits.