E-commerce & Retail Scraper API

Every API in this category

Send a public page URL to the category endpoint. The target website determines which fields can be extracted; there is no social-media-style scraper name to supply.

Fields depend on the target and request context. A dedicated guide is not a guarantee that every field is available on every page.

The 63 dedicated pages

Choose a guide for your target. This list is generated from the same category data as the catalogue and structured page list.

How a Retail API call works

Retail requests are synchronous: submit a public product URL and read the structured result from the same response.

STEP 1Send the product URL and only the rendering or proxy options required by that target. Authenticate with your username and API key.

curl --request POST 'https://api.scraping-bot.io/scrape/retail' \
  --user "YOUR_USERNAME:YOUR_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "url": "https://www.amazon.com/dp/PRODUCT_ID",
  "options": {
    "useChrome": false,
    "premiumProxy": false
  }
}'

Replace PRODUCT_ID with a real public product identifier before running the example.

STEP 2Read the data object and inspect the returned target status before saving product fields.

Request parameters

See the documentation for the complete request and response examples.

Credits, refunds and limits

Current plans start at 1 credit for a standard Retail call. Legacy Retail plans use a different base rate (10 credits before applicable options). PrestaShop is a separate integration and is not covered by the Retail cost table.

Request limits depend on your plan. Respect rate-limit responses, avoid uncontrolled retries and check target-specific proxy requirements. Additional targeting or special-domain rules can affect costs; confirm your configuration in the pricing plans and documentation.

Retail API or Raw HTML scraper?

Questions about the E-commerce & Retail API

Do I need a scraper name?

No. Send a product URL to /scrape/retail; the target website determines the extraction. Named social media scrapers use a different endpoint.

Can I scrape a whole product catalogue in one call?

This endpoint takes a page URL. Do not assume a single request crawls an entire store; plan your URL collection and request volume separately.

Are all product fields always available?

No. Price, stock and identifiers depend on what the target page exposes and what its extractor supports. Check the dedicated guide and inspect the response.

Which data should I collect?

Use public pages and collect only the data needed for your use case. Public availability does not remove privacy, copyright or contractual obligations; assess those before using or republishing the results.

Other categories