URL → JSONAny siteFree tier

Product Page Scraper API — URL → JSON

Drop in any product URL, get back structured JSON. Title, price, currency, brand, EAN, description, images, availability — extracted from any e-commerce site without writing a parser. One endpoint covers them all.

Highlights

What is included

Any retailer URL

No site-specific config needed. Send a product URL from any e-commerce site and we extract the canonical product fields.

Structured JSON

Title, price, currency, brand, EAN, GTIN, availability, description, image array. Predictable schema across every site.

Sub-3-second response

Single round-trip. No browser orchestration on your side, no proxy management, no anti-bot retries.

1 credit per call

Same pricing as marketplace endpoints. 100 free credits to evaluate, no credit card required.

When to use the page extractor vs a marketplace endpoint

If the product is on Amazon, bol.com, Coolblue, or Google Shopping, the marketplace-specific endpoint will give you richer fields (Buy Box, ASIN, multiple sellers, variants). The page extractor is for everything else: brand DTC sites, niche retailers, supplier catalogs, blog product mentions.

  • Marketplace endpoints (offers/info/buybox) → use when you have an EAN and the product is on a supported marketplace.
  • Page extractor (/page) → use when you only have a URL, or the source isn't a marketplace we have a dedicated endpoint for.
  • Both endpoints return predictable JSON; mix them in the same pipeline.

Common use cases

The page extractor is the workhorse for catalog ingestion, competitive monitoring of indie retailers, and DIY price-comparison apps.

  • Onboard a new supplier: paste their PDP URLs and get GTIN-keyed JSON for your PIM in minutes.
  • Monitor a competitor's DTC site (no marketplace listing, no public API).
  • Build a price-comparison app: throw 100 URLs at the endpoint, get 100 normalized JSON records.
  • Enrich a sparse data feed: supplier sends only URLs, you need title/brand/image for your storefront.
  • Validate a product page is reachable and well-formed before you list it.
API

Page extractor API

Get started in minutes with code examples in your preferred language.

Page — extract product JSON from any URL

Pass any product URL. Returns the canonical product fields: title, price, currency, brand, EAN/GTIN, description, images, availability. 1 credit per call.

View in API guide

Implementation

curl -X GET "https://api.shoppingscraper.com/page?url=https%3A%2F%2Fwww.coolblue.nl%2Fproduct%2F930181%2Fsony-wh-1000xm4-zwart.html&raw=true&api_key=your_api_key_here"
GEThttps://api.shoppingscraper.com/page?url=https%3A%2F%2Fwww.coolblue.nl%2Fproduct%2F930181%2Fsony-wh-1000xm4-zwart.html&raw=true&api_key=your_api_key_here
API Response
{
"url": "https://www.coolblue.nl/product/930181/sony-wh-1000xm4-zwart.html",
"title": "Sony WH-1000XM4 Wireless Headphones",
"price": "49.99",
"price_currency": "EUR",
"availability": "InStock",
"brand": "Zazu",
"gtin": "8718924881156",
"description": "Product description...",
"images": ["https://..."],
"success": true
}

Frequently Asked Questions

What sites does the page extractor support?+

Any e-commerce product page. We don't maintain a per-site allowlist — pass a URL and we extract the canonical product fields. For Amazon, bol.com, Coolblue, and Google Shopping you'll get richer data from the dedicated marketplace endpoints, but the page extractor handles every other retailer.

What does the response include?+

Title, price, currency, brand, EAN/GTIN (when present in the page), description, image URLs, and availability. The schema is the same across every site — no per-source mapping needed in your code.

How is this different from your marketplace endpoints?+

Marketplace endpoints return marketplace-specific fields like ASIN, Buy Box winner, every seller offer, or product variants. The page extractor handles ANY product page on the open web with a unified schema. Use marketplace endpoints when you have an EAN and the product is on a supported marketplace; use the page extractor for everything else.

Does it work on JavaScript-heavy single-page apps?+

Yes. We render the page server-side and extract the final DOM, so SPAs that hydrate prices client-side still resolve correctly.

What does it cost?+

1 credit per call, same as the marketplace offers/info endpoints. The free tier includes 100 credits — enough to evaluate the endpoint on a real workload before signing up.

Can I use this for catalog ingestion at scale?+

Yes. Pair the page extractor with a Scheduler to ingest hundreds or thousands of URLs on a recurring schedule, with reports delivered as CSV/XLSX. Concurrency is capped at 100 connections per API key.

Start extracting product data from any URL

100 free API calls. No credit card. Same endpoint, every retailer.