Amazon Scraper quickstart

Request one Amazon product with cURL and read its structured result. This walkthrough uses the request example from the Product API reference.

Before you begin

You need a Scrapeless account, a valid API key, and cURL. Get your key from the Scrapeless dashboard.

The sample uses a product URL from the API reference. You can replace it with the Amazon product URL you want to retrieve. Listing availability and returned values may change.

1. Send the request

Replace YOUR_API_KEY with your key:

curl --request POST 'https://api.scrapeless.com/api/v1/scraper/request' \
  --header 'x-api-token: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "actor": "scraper.amazon",
  "input": {
    "type": "product",
    "url": "https://www.amazon.com/dp/B0BQXHK363",
    "zip_code": ""
  }
}'

The body selects the Amazon actor, sets type to product, and provides the product url. The empty zip_code matches the official example; provide a postal code when you need delivery information for that location.

2. Read a completed result

HTTP 200 indicates completion. The following is a field subset of the published Product response example, not a fresh capture:

{
  "asin": "B0BQXHK363",
  "availability": "In Stock",
  "final_price": "$44.99",
  "rating": "4.0",
  "reviews_count": "115"
}

Prices, ratings, and review counts in this example are strings. Preserve the returned types when reading the payload, and convert them explicitly if your application needs numeric values. Other fields in the full example include title, images, and variations.

3. Retrieve a task that is still processing

An HTTP 201 response returns a task ID. The API reference shows:

{
  "message": "task in progress",
  "taskId": "a8af123c-0f81-477d-a2e7-c57ad18fe54a"
}

Use the ID from your own response, not the example ID, in this request:

curl --request GET 'https://api.scrapeless.com/api/v1/scraper/result/YOUR_TASK_ID' \
  --header 'x-api-token: YOUR_API_KEY'

If the task is still processing, continue according to Results and Polling. Use a bounded retry policy instead of repeatedly submitting the same product request.

If the request fails

Inspect both the HTTP status and response body. The Product reference includes a 400 example with code: 20500 and message: "scraping failed". Check the key, product URL, and JSON input. Follow the shared polling guide for rate limits and server errors.

Next steps

Continue to Endpoints for Seller, Keyword search, and Rufus requests. Review the Product API reference for the complete published example.

Introduction Endpoints