Best Google Shopping APIs in 2026: 10 Providers Compared

The best Google Shopping API depends on what you need per product. If you need every seller for a product in one request, CrawlerData and Scrapingdog’s product endpoint are the simplest flows. If you need reviews, city-level locations or dozens of other Google engines, SerpApi, SearchApi, Oxylabs and DataForSEO cover more ground. If you run large, non-urgent batches, DataForSEO’s queued Merchant API is pay-as-you-go and its balance never expires.

Below we compare 10 providers on endpoints, sellers per call, cost per 1,000, cost per product and billing rules. Prices are as of October 2026.

Quick answer: which Google Shopping API fits your use case

Listed by use case, not ranked:

• Every seller per product in one call, no pagination: CrawlerData (1 credit per 10 sellers returned, rounded up; 1 credit per request on other endpoints).
• Cheapest per product call at high volume: Scrapingdog’s /google_product with offers=1 (5 credits per call).
• Large batch jobs that can wait: DataForSEO Merchant API (task-based, balance never expires).
• Deepest product data (reviews, specs, variants) plus many other Google engines: SerpApi or SearchApi.
• Rendered pages and broad scraping beyond Google: Oxylabs or Bright Data.
• Low-code, per-result pricing: Apify community actors.

“Google Shopping API” means two different things

If you search for “Google Shopping API”, Google’s own developer docs show up. Those are a different product. Google’s Merchant API (the successor to the Content API for Shopping) lets a merchant manage its own product feed, prices and inventory in Merchant Center. It does not return other merchants’ listings or prices.

This post covers the other meaning: APIs that return data from public Google Shopping results, such as products, prices, sellers and ratings for any search query or product. That is what price monitoring, competitor tracking and market research need, and it’s sold by third-party providers.

How Google Shopping data is fetched in 2026

Search, then product token, then offers

Most providers now use three steps:

1. Shopping search returns a list of products, each with a product ID or a token.
2. Product call takes that token and returns details: title, specs, ratings, and often a first page of offers.
3. More offers need extra calls, either a “more stores” switch or page tokens.

That third step is why “price per 1,000 searches” understates the cost of a product with 30 sellers.

Recent changes worth knowing

• Oxylabs discontinued its google_shopping_pricing source. Its changelog (2025-10-08) says pricing data now comes from google_shopping_product (Oxylabs docs).
• SearchApi removed product_id and prds from its Product and Product Offers endpoints on 2026-05-15. A product_token from a Shopping call is now required (SearchApi docs).
• ScraperAPI’s Shopping endpoint returns a link that “must be requested separately” to get product details, sellers and offers, so sellers take a second request (ScraperAPI docs).

How we compared

• Sources: public pricing and docs pages, checked on 12 October 2026 and linked below.
• No benchmarks. We haven’t run a controlled speed or success-rate test across vendors, so we don’t publish one.
• Unknowns stay unknown. Where a page is silent, or two official pages disagree, we say so instead of guessing.

Comparison tables

Endpoints

“Not found” means we didn’t find it in the docs we checked, not that it can’t exist.

How sellers are returned

Cost per 1,000 Shopping searches (entry plan)

Providers

Alphabetical. Every price is as of October 2026 and links to the page we read.

Apify (community actors)

Apify sells a platform plan ($0 to $999 per month, Apify pricing) plus per-result fees set by each actor. There is no official Apify Google Shopping actor; the ones we checked are community-built. The scrapewise actor charges $2.50 down to $2.00 per 1,000 products, plus $0.02 per product and $0.02 per extra page of 10 stores for store offers, and doesn’t charge for empty, duplicate or blocked results. Unused monthly platform usage expires at the end of the cycle.

Best for: no-code runs with per-result pricing. Limitations: actor terms change often.

Bright Data

Bright Data’s SERP API returns Shopping results inside Google searches via udm=28, with uule and city-level targeting (Bright Data docs). Product listings, merchants and specifications come from a separate Google Scraper API dataset. SERP pricing is $1.50 per 1,000 pay-as-you-go, or $499 per month for 380k requests on Scale (Bright Data pricing), with 5k free requests a month. Failed requests aren’t billed, except in zones using custom headers or cookies (billing docs).

Best for: location-heavy work across 195 countries and teams already using Bright Data. Limitations: a Shopping-specific dataset price isn’t stated on the pricing page.

CrawlerData

Our Google Shopping API returns products with price, merchant, rating and product_id. The Sellers API returns every seller for a product in one request, sorted by total price, with merchant, price, shipping, total and availability. The Product API returns title, brand, description, images, rating and specs. Search and product requests cost 1 credit each; the Sellers API costs 1 credit per 10 sellers returned, rounded up, minimum 1 (22 sellers = 3 credits). Credits cost $1.00 per 1,000 on the $50 pack, down to $0.30 on the largest (pricing). Failed requests aren’t charged and credits are valid for 6 months.

Best for: price monitoring where you need all sellers in one request, with cost that scales with the sellers actually returned. Limitations: see “Where CrawlerData is weaker” below.

DataForSEO

DataForSEO’s Merchant API has Products, Product Info, Sellers, Sellers Ad URL and Reviews endpoints, available as Standard tasks (POST, then GET) only, with no Live mode (DataForSEO docs). Products, Product Info and Sellers cost $0.001 on Standard (about 45 minutes) or $0.002 on Priority (about 1 minute) (Merchant pricing). Products bill per block of 40 results. For Sellers, the billing note says per block of 10 sellers, while the price table reads as “per product/seller”, so treat that unit as unconfirmed. Balances never expire and failed requests aren’t charged (FAQ); the minimum payment is $50.

Best for: large scheduled batches and teams who also want keyword and SEO data. Limitations: asynchronous only for Shopping.

Oxylabs

Oxylabs offers google_shopping_search and google_shopping_product, which returns online sellers, reviews (US locale only), variants and specifications (Oxylabs docs). Both need render: "html", so we assume the Google JS rate: $1.35 down to $0.90 per 1,000 (Oxylabs pricing), our arithmetic. 2xx and 4xx responses are billed (billing), and unused balance expires at cycle end.

Best for: teams who need rendering and one subscription across many targets. Limitations: 4xx billing; extra sellers only from the first “More stores” expansion.

ScraperAPI

ScraperAPI’s structured /structured/google/shopping endpoint returns title, merchant, price and delivery as JSON or CSV (ScraperAPI docs). Sellers and offers need a second request to the returned link. Its credits page lists 25 credits for Google domains, but it doesn’t state whether structured endpoints use that weight, so we don’t compute a per-1,000 price. Plans run from $49 per month for 100k credits (pricing); 200 and 404 responses are billed.

Best for: existing ScraperAPI users. Limitations: two requests per product with sellers; per-call cost not published.

SearchApi

SearchApi lists Google Shopping, Product, Product Offers, Product Specs, Product Reviews and more (SearchApi docs). Its Shopping search can resolve Google redirects to merchant URLs with link=resolved. Product Offers returns 5 offers on page 1 and up to 10 on later pages (Product Offers docs). Plans run from $40 for 10,000 searches to $5,000 for 5M (pricing); only 200 responses are charged.

Best for: teams who want a broad catalogue of Shopping sub-endpoints plus about 40 other engines. Limitations: whether Product and Product Offers calls cost 1 search each isn’t stated.

SerpApi

SerpApi’s Google Shopping engine returns about 40 items per page with location, uule, device and price filters (SerpApi docs). Its Immersive Product engine returns stores with price, shipping, total and stock, plus specs, ratings and reviews (docs). Plans run from $25 for 1,000 searches to about $1.96 per 1,000 on its largest listed plan (our arithmetic; pricing). Failed, errored and cached searches are free. SerpApi also lists a Google Product engine (docs); we haven’t tested it.

Best for: the richest product pages, city-level locations and devices, and the widest engine catalogue. Limitations: high cost per search at entry tiers; whether each extra stores page bills as one search isn’t stated.

Scrapingdog

Scrapingdog’s /google_shopping costs 10 credits per successful request; /google_product costs 5 credits and takes offers=1, specs=1 and reviews=1 (Scrapingdog docs). Plans run from $40 for 200k credits to $30,000 for 1.1B (pricing). Failed, blocked and timed-out requests are refunded. Its immersive product endpoint is listed at 5 credits on one page and 10 on another, so we leave it out of the math.

Best for: the lowest list cost per product call at high volume. Limitations: credit weights differ between pages; sellers per call aren’t stated.

ValueSERP

ValueSERP (now redirecting to Traject Data) supports search_type=shopping and product requests with online_sellers, reviews and specifications (ValueSERP docs). Plans start at $50 per month for 25,000 searches, billed annually (pricing); the page states $1.60 per 1,000 for that tier, while the plan price works out to $2.00. Only successful searches are counted.

Best for: batch jobs of up to 10,000 searches. Limitations: credit cost per product request isn’t stated; parameter table and examples disagree on one value.

Also has Shopping search

Serper lists a Shopping endpoint on its homepage, but we found no product, sellers or reviews endpoint. Zenserp lists Shopping Search and a Shopping Product Page endpoint (docs), but its product docs page returned an error, so we couldn’t confirm what it returns.

Cost per product with ~30 sellers

This is the number price-monitoring teams care about. Assumptions: one product with about 30 sellers, list prices on 12 October 2026, excluding the search call that finds the product, and only documented page sizes. Corrections welcome.

Caveats: Scrapingdog doesn’t state how many sellers one call returns. SearchApi and SerpApi don’t state that each offers page costs one search. CrawlerData charges 1 credit per 10 sellers returned, rounded up, so a product with 30 sellers is 3 credits and one with 8 sellers is 1 credit. Scrapingdog’s product call is cheaper than CrawlerData for a 30-seller product on both entry and largest plans, so if it returns all the sellers you need, it wins on price. At entry prices DataForSEO’s Standard queue ($0.003) costs the same as CrawlerData’s Starter pack; on our largest pack ($0.0009) CrawlerData is cheaper than DataForSEO, and you get the result live instead of from a queue. Others aren’t computable from public pages.

Billing rules that change the real cost

Where CrawlerData is weaker

• It’s a newer product, with a shorter track record than most providers here.
• Fewer endpoints. We have 8 Google endpoints. SerpApi and SearchApi each list about 40 engines, and we don’t return product reviews.
• Country-level only. We cover 31 countries with no city or uule targeting. SerpApi, Bright Data and DataForSEO offer finer locations.
• Small trial. 50 free credits, valid 30 days, with a verified work email. Bright Data gives 5k requests a month and SerpApi 250 searches a month.
• Shopping product and sellers requests can take tens of seconds.
• Page 1 only for Shopping search.
• Lower rate limits: 100 requests per minute and 20 per second per API key.

How to choose

Answer these before you pick:

1. Sellers per product: if you need all of them, check offer page sizes and how extra pages bill.
2. Locations: country-level suits most price monitoring; local work may need cities.
3. Latency: queued APIs can take minutes; live product requests can take tens of seconds.
4. Volume: compare the per-call price at your real tier, not the entry price.
5. Reviews, specs, variants: only some providers return all three.
6. Billing: failed and empty responses, and expiry (table above).

For a deeper look at the numbers, see our Google Shopping API pricing comparison. If you’re moving from SerpApi, read SerpApi alternatives.

Changelog

• 2026-10-12: First published. All prices and docs checked on this date.
• 2026-10-12: Updated CrawlerData seller pricing (1 credit per 10 sellers).