Monitor Sellers

API Playground is ScraperAPI's request builder for testing and configuring scraping requests. In this tutorial, you will use the API Playground to monitor sellers and MAP violations across your Amazon catalog. By the end, you will have a daily batch job that flags unauthorized sellers and price violations across every listing, so you can protect brand pricing without an enforcement team.

Step 1: Configure the Amazon Offers endpoint

Open the API Playground from the left sidebar.

Select scraping method: Structured Data Endpoints.
In the endpoint dropdown, select Amazon Offer.
Enter ASIN B0BFC7WQ6R. Set Country to us.
Review the Summary panel on the right to understand the cost of the job before you run it.
Scroll down to the generated code and click Try it.

The Playground runs the request and shows the response inline. Each entry in the listings array includes seller_name, price, shipping_price, condition, pinned_offer, and fullfilled_by_amazon.

Use the language dropdown to switch to Python, Node.js, PHP, Ruby, or Java. Click Copy to clipboard to run the request in your own terminal instead.

Step 2: Additional options and filters

Use Additional options & filters to fine-tune your request. The Playground adds the relevant parameters to the generated code automatically.

Country code adds country_code. Targets a specific Amazon marketplace — use gb for Amazon UK, de for Germany, and so on.
Domain adds domain. Sets the Amazon domain (e.g. co.uk, com.au).
Output format adds output_format. Returns results as json (default) or csv.
Condition adds condition. Filters offers by item condition (e.g. new, used).
Activate retrying 404 responses adds retry_404. Retries requests that return a 404 instead of treating them as final.

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

Step 3: Prepare your reference files

authorized_sellers.txt — one seller name per line:

Official Brand Store
Authorized Distributor West
Brand Direct

map_prices.csv — ASIN and minimum advertised price:

B0BFC7WQ6R,24.99
B08KHL5KKL,49.99
B086B88TGR,14.99

Step 4: Submit a batch across your catalog

Switch the scraping method to Async in the Playground and paste your ASINs as full structured endpoint URLs, one per line:

https://api.scraperapi.com/structured/amazon/offers?asin=B0BFC7WQ6R&country=us
https://api.scraperapi.com/structured/amazon/offers?asin=B08KHL5KKL&country=us
https://api.scraperapi.com/structured/amazon/offers?asin=B086B88TGR&country=us

Step 5: Poll for results

Async jobs run in the background. Use the statusUrl from the batch response to check progress. When status is finished, read response.body from each job result. Compare seller_name against authorized_sellers.txt and price against map_prices.csv. Flag any seller not on the allowlist, and any price below the MAP threshold.

STATUS_URL="https://async.scraperapi.com/jobs/YOUR_JOB_ID"

while true; do
  STATUS=$(curl -s "$STATUS_URL" | python3 -c "import sys,json; print(json.load(sys.stdin)['status'])")
  echo "Status: $STATUS"
  if [ "$STATUS" = "finished" ]; then break; fi
  sleep 10
done

Step 6: Deliver to cloud storage and skip polling

Instead of polling, configure a destination in your dashboard under Destinations and add a callback to your batch request. Results land in your bucket automatically when each job finishes — ready for your violation check script to process.

curl -X POST "https://async.scraperapi.com/batchjobs" \
  -H "Content-Type: application/json" \
  -d '{
    "apiKey": "API_KEY",
    "urls": ["..."],
    "callback": {
      "type": "s3",
      "url": "my-destination-name"
    }
  }'

Step 7: Schedule daily

To run your batch automatically on a recurring schedule, add it to your crontab. The example below runs every day at 6am.

0 6 * * * /usr/bin/bash /path/to/monitor_sellers.sh >> /var/log/seller_monitor.log 2>&1

Prefer a no-code setup? Monitor sellers with DataPipeline instead.