Amazon Scraper endpoints

Use the actor scraper.amazon for every operation on this page. Select the operation with input.type and provide its corresponding inputs.

Request and authentication

POST https://api.scrapeless.com/api/v1/scraper/request
x-api-token: YOUR_API_KEY
Content-Type: application/json

Replace YOUR_API_KEY with your Scrapeless API key. Send one JSON object containing actor and input.

Choose an operation

Operation	`input.type`	Inputs used below
Product	`product`	`url`, `zip_code`
Seller	`seller`	`url`, `zip_code`
Keyword search	`keywords`	`keywords`, `page`, `domain`, `zip_code`
Rufus	`rufus`	`keywords`, `domain`

Product

Provide an Amazon product URL. The Product schema requires url; zip_code supplies delivery-location information.

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 published response includes asin, title, availability, final_price, rating, reviews_count, images, and variations. See Quickstart for a shortened response example.

Product API reference

Seller

Provide a seller page URL. Include zip_code: the Seller schema marks it as required, and its request example uses an empty string.

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": "seller",
    "url": "https://www.amazon.com/sp?seller=A2XZ7JICGUQ1CX",
    "zip_code": ""
  }
}'

The Seller reference defines the successful response as a JSON object without a field-level schema or example. Inspect the returned payload before mapping seller fields in your application.

Seller API reference

Keyword search

Provide search text in keywords. Use page to select a search-results page. The example below follows the documented numeric page value and uses domain: "com" for Amazon.com; it omits the optional department filter.

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": "keywords",
    "keywords": "Iphone+14+Pro+512GB",
    "page": 1,
    "domain": "com",
    "zip_code": ""
  }
}'

Input	Use
`keywords`	Search keywords; required by the operation schema.
`page`	Search-results page number.
`domain`	Amazon domain setting; the official example uses `com`.
`department`	Optional department alias, corresponding to Amazon’s `i` query parameter.
`zip_code`	Postal code for delivery information.

The published response has keyword, page, result, total_results_count, and url. Product entries appear under result.organic. The response example is for a different query and page from the request example, so it should be used to understand fields rather than predict exact results.

The Amazon parameter guide specifies integer page values, and the request example uses 1; the generated operation schema currently labels page as a string. This guide follows the parameter guide and request example.

Keyword search API reference

Rufus

Set type to rufus. Both keywords and domain are required by the operation schema. Use a full Amazon domain, such as www.amazon.es, rather than the com format used in the Keyword search example.

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": "rufus",
    "keywords": "macbook",
    "domain": "www.amazon.es"
  }
}'

The published response contains:

Field	Content shown in the API example
`html`	Raw content containing event records and HTML fragments.
`metadata`	Includes `type` and `rawUrl`.
`result.user_query`	Query text.
`result.products`	Product entries returned for the query.
`result.related_questions`	Related questions.

The operation schema also lists is_sse_data, is_get_question, and asin, but does not explain their behavior. Start with the documented request above.

Rufus API reference

Handle task results

An HTTP 200 response contains the completed result. An HTTP 201 response means processing is still underway; save its taskId and retrieve that task with:

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

Replace YOUR_TASK_ID with the ID returned by your request. Follow Results and Polling for polling intervals and retry limits.

Inspect error bodies as well as HTTP status codes. A 400 response can include code: 20500 and message: "scraping failed"; it is not a successful data response. Check the target and request inputs before retrying.

Parameter reference

Use Amazon API Parameters for the department aliases and other documented inputs. Parse results for the selected type; Product, Keyword search, Seller, and Rufus do not share a single field layout.

Quickstart Introduction