Getting Started with Product Data Extraction in 2026

Most people who sign up for Product Scrapes want the same thing: give it a product URL, get back clean JSON with the title, price, image, and availability. This post covers how to do exactly that.

#Get your API key

Create an account at productscrapes.com. You'll get a handful of free demo lookups so you can test things out before committing.

Once you're in, grab your API key from the dashboard.

#Make a request

Pass any product URL to the /api/fetch endpoint:

curl -X POST https://productscrapes.com/api/fetch \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.amazon.com/dp/B0EXAMPLE"}'

You'll get back something like this:

{
  "data": {
    "product": {
      "title": "Wireless Bluetooth Headphones",
      "description": "Premium noise-cancelling headphones...",
      "price": "79.99",
      "currency": "USD",
      "image_url": "https://example.com/image.jpg",
      "brand": "AudioTech",
      "sku": "AT-WBH-100",
      "in_stock": true
    }
  }
}

The title, description, and price fields are present on almost every product. Others like sku and brand depend on what the store actually exposes - some sites are better about this than others.

#What data you get back

"Depends on the store" is doing a lot of work in that table. Amazon gives you almost everything. A random Shopify store might only give you title, price, and an image. That's just the nature of scraping - different sites structure their data differently, and we normalise what we can.

#Which stores work

We support thousands of e-commerce sites, but the ones people ask about most:

• Amazon across 11 supported regions (US, UK, DE, FR, IT, ES, CA, AU, NL, SE, SA)
• Any Shopify store - if it runs on Shopify, we can pull from it
• WooCommerce sites
• eBay, Target (US), Best Buy (US/CA)

If you're unsure whether a specific store works, just try it. The demo lookups are free and you'll get an instant answer.

#A few things I'd recommend

Store the full API response somewhere, not just the fields you're using right now. I've seen people strip responses down to just title and price, then six months later wish they had the brand and image_url too. Raw responses are cheap to store.

Cache aggressively. If you're checking the same product page multiple times a day, you probably don't need fresh data every time. Cache for at least an hour unless you're doing time-sensitive price monitoring.

Handle missing fields. Not every product will have every field populated. Your code should expect null values and not blow up when brand comes back empty.

#What to build next

If you've got data flowing, the next step depends on what you're building. The most common things we see people do:

• Track prices over time and alert on drops (we wrote a tutorial on that)
• Build product comparison pages
• Feed data into affiliate marketing sites (affiliate link generation coming soon)
• Enrich an existing product catalogue with images and descriptions from other retailers