Google Shopping APIFetch Google Shopping search, product detail, reviews, and sellers as structured JSON with one SocialCrawl API key. Shared commerce schema. Reads are priced in credits.
5 active endpoints. Search is advanced tier.
Five live read endpoints for Google Shopping. Keyword search returns ids for product, reviews, sellers, and price history. Data API only. Task polling is handled server-side.
/v1/google_shopping/product-searchKeyword search on Google Shopping. Returns product cards plus opaque ids (product_id, gid, data_docid) for detail legs. First calls can take ~20-30s. Advanced tier (5 credits).
query, country, language, depth, price_min, price_max, sort_by
/v1/google_shopping/productProduct detail from ids returned by product-search. Pass product_id, gid, or data_docid. Standard tier (1 credit).
product_id or gid or data_docid, country, language
/v1/google_shopping/reviewsReviews for a Google Shopping product. Prefer gid from search. Standard tier (1 credit).
gid, product_id, data_docid, depth, country, language
/v1/google_shopping/sellersSeller and offer rows for a product id from search. Standard tier (1 credit).
product_id or gid or data_docid, country, language
/v1/google_shopping/price-historyDated price observations per store for a product_id from product-search. A time series, not the current listing.
product_id, country
Returns Google Shopping products matching a keyword: title, seller, current and original price, rating, images, and the ids needed to fetch more detail.
Use it as the entry point for Google Shopping, since product, reviews, and sellers all need an id it returns.
5 credits
query · Product search keyword (e.g. 'wireless earbuds').
$ curl https://www.socialcrawl.dev/v1/google_shopping/product-search?query=wireless+earbuds \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key. Hit "Try it" to see an example responseGoogle Shopping is a normal SocialCrawl data surface. You call GET /v1/google_shopping/… with an API key, spend credits on live misses, and get a single JSON envelope back.
Send your key in the x-api-key header. No Google Shopping OAuth app for public reads. The same key works across SocialCrawl platforms.
All Google Shopping routes are GET. Pass query, product_id, gid, data_docid, country, language, depth as query strings. We validate formats before charging.
product-search costs 5 credits. product, reviews, and sellers cost 1 credit. The first task can take tens of seconds, then cache.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.
Most products discover entities first, then deepen detail and reviews only when needed.
GET /v1/google_shopping/product-search?query=…ProductList with product_id, gid, data_docid
Ids are required for every deepen call.
GET /v1/google_shopping/product?product_id=…Product detail from opaque ids
Search cards are not a full product record.
GET /v1/google_shopping/reviews?gid=…ReviewList for the product
VoC on Shopping reviews.
GET /v1/google_shopping/sellers?product_id=…SellerList of offers
Cross-merchant price rows.
GET /v1/google_shopping/product-search?query=wireless+earbuds
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
GET /v1/google_shopping/product?product_id=1749519698216963169
GET /v1/google_shopping/reviews?gid=3591805395819257241{
"success": true,
"data": {
"items": [
{
"product": {
"id": "1749519698216963169",
"title": "Example earbuds",
"price": { "current": 39.99, "currency": "USD" },
"rating": 4.4,
"ext": { "gid": "3591805395819257241" }
}
}
]
},
"credits_used": 5,
"credits_remaining": 9995,
"request_id": "req_…",
"cached": false
}Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.
id, title, price, rating, images, ext ids
items[] with ids required for deepen legs
items[] with rating, text, author
merchant offer rows
Same request lifecycle as every other /v1 platform endpoint. Google Shopping is not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
Registry lookup finds google_shopping/product-search (or product, reviews, sellers). Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before upstream work.
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the task lifecycle is spin-polled server-side. Retries on 5xx/network with a circuit breaker if the source is unhealthy.
Upstream JSON is mapped to commerce archetypes (Product, ProductList, ReviewList, SellerList, App, PlaceList as applicable), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
Google Shopping is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.
Public Shopping search, product info, reviews, and seller offers. Read-only.
Shopping reads run as server-side tasks. The async lifecycle is hidden; you get one synchronous HTTP call.
ProductList with opaque ids, then Product, ReviewList, SellerList.
No Merchant Center management, ads, or feed upload.
The jobs this API is most often used for.
Cross-merchant price and review research
Callers always start at product-search. product, reviews, and sellers need ids from that response. Synchronous Shopping search with server-side tasks, then 1-credit deepen legs for product, reviews, sellers.
Cold product-search often runs about 20-30s. Cached deepen calls are typically a few seconds.
The jobs Google Shopping data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Common ways teams put this data to work, and the stack each one tends to run.
product-search then sellers for multi-merchant quotes.
reviews via gid for product sentiment.
product detail from search ids for attribute capture.
Search is 5 credits. Product, reviews, and sellers are 1. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/google_shopping/product-search?query=wireless+earbuds" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/google_shopping/product?product_id=1749519698216963169" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Same Google Shopping data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | DIY scraping |
|---|---|---|
| Authentication | One x-api-key header across 65 platforms | None: you manage proxies and browser fingerprints instead |
| Setup | One GET request; ids chain search → product → reviews → sellers | Headless browser, proxy pool, and HTML parsers to build before the first result |
| Rate limits / blocks | Flat credit pricing; blocks handled upstream | Google Shopping renders client-side and blocks bots aggressively |
| Response schema | Unified commerce schema shared with Amazon and Trustpilot endpoints | Raw HTML and embedded JSON you reverse-engineer after every layout change |
| Pricing | 5 credits per search, 1 credit for product, reviews, and sellers; 100 free | Free to attempt, but proxy and CAPTCHA costs grow with volume |
| Maintenance | Stable schema maintained as Google Shopping evolves | Selectors break silently whenever Google ships a redesign |
Authentication
Setup
Rate limits / blocks
Response schema
Pricing
Maintenance
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl