Monitor Sellers

DataPipeline is ScraperAPI's no-code dashboard for scheduled scraping. In this tutorial, you will use DataPipeline to track seller activity and MAP violations across your Amazon catalog. By the end, you will have a daily feed of every seller on every listing, so you can identify unauthorized sellers and price violations before they affect your margins.

Step 1: Create the project

Click DataPipeline in the left sidebar.

Select New Project.
Select Amazon offers.

Step 2: Configure input settings

Under Input settings, choose List and enter your ASINs, one per line:

B0BFC7WQ6R
B08KHL5KKL
B086B88TGR

For larger catalogs, switch to Upload file and upload a CSV with one ASIN per row.

Step 3: Configure output settings

Under Output settings, choose Download. Results will be available in the dashboard when the job completes. For automated violation detection, enter a Webhook URL instead so results are posted to your server as they arrive.

Step 4: Set scraping frequency

Under Scraping frequency, select Just scrape once. To monitor sellers on a recurring basis, switch this to Daily, Weekly, or another interval. Recurring schedules require a paid plan.

Step 5: Review and start

Click Review & start scraping. The Job summary panel shows the estimated credit cost before you confirm.

Step 6: Review results

Click into the project after the run completes and click Download results. Results are retained for 30 days.

Compare seller_name against your authorized-sellers list and price against your MAP thresholds to flag violations.

Amazon offers and Amazon product pages are separate project types. If you want both offer-level and product-level data, create two separate projects and correlate them by ASIN.

Additional options

Under Additional options & filters you can fine-tune your requests:

Country code: targets a specific country's Amazon marketplace.
Domain: sets the Amazon domain to search (e.g. co.uk, com.au).
Condition: filters offers by item condition (e.g. new, used).
Activate retrying 404 responses: retries requests that return a 404 instead of treating them as final.

Some parameters increase the cost per request. Check the Cost per Job panel before committing to a configuration at scale.

Prefer to set this up in your own codebase? Try the API playground instead.