amazon.de APIamazon.de ↗
Access Amazon.de product search, details, reviews, bestseller lists, seller info, and autocomplete suggestions via a single structured JSON API.
curl -X GET 'https://api.parse.bot/scraper/450e804c-e517-40a7-987e-2b96bb99b1df/search_products?query=laptop' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for products on Amazon.de by keyword. Returns paginated results. Pagination and filter parameters may occasionally trigger upstream 503 errors from Amazon rate-limiting.
| Param | Type | Description |
|---|---|---|
| rh | string | Amazon filter parameter (rh) for category or price filters. May trigger upstream errors on some values. |
| page | integer | Page number for pagination. |
| queryrequired | string | Search keyword |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"query": "string, the search keyword used",
"products": "array of product objects with asin, title, url, price, currency, rating, reviews_count, image_url, is_sponsored, is_prime",
"total_results_text": "string or null, results count text from Amazon"
},
"sample": {
"data": {
"page": 1,
"query": "laptop",
"products": [
{
"asin": "B0F8F3NNS6",
"price": "497,33",
"title": "Lenovo IdeaPad Slim 3i Laptop | 14\" WUXGA Display | Intel Core i5 13420H | 16GB RAM | 512GB SSD",
"currency": "€",
"is_prime": false,
"image_url": "https://m.media-amazon.com/images/I/71SdHx+ytKL._AC_UY218_.jpg",
"is_sponsored": false
}
],
"total_results_text": ""
},
"status": "success"
}
}About the amazon.de API
The Amazon.de API covers 6 endpoints that return structured product data from Amazon's German marketplace, including search results, individual product details, customer reviews, seller offer information, bestseller rankings, and autocomplete suggestions. The search_products endpoint returns up to a full paginated result set with fields like asin, price, rating, reviews_count, is_sponsored, and is_prime for each matched product.
Product Search and Details
The search_products endpoint accepts a query string and optional page and rh filter parameters. The rh parameter mirrors Amazon's own category and price filter syntax, allowing narrowed searches by department or price band. Each result object includes asin, title, url, price, currency, rating, reviews_count, image_url, is_sponsored, and is_prime. Note that certain rh values or high page numbers may return upstream 503 errors due to Amazon's own rate-limiting on the German storefront.
The get_product_details endpoint takes a single asin and returns a richer set of fields: brand, price, stars, title, images (array), rating, description (feature bullets), availability, and a specifications key-value object. Some fields may be null depending on how a given product page is structured — this is especially common for third-party or low-traffic ASINs.
Reviews, Sellers, and Bestsellers
The get_product_reviews endpoint returns up to 8–13 reviews per call from the product page. Each review object contains id, author, rating, title, body, date, and verified status. The endpoint also surfaces total_ratings and overall_rating text. Pagination beyond page 1 is not currently supported — all reviews come from a single product page view.
The get_seller_info endpoint returns the main_offer object for an ASIN, with fields for price, ships_from, sold_by, merchant_info, and availability. The get_bestsellers endpoint accepts an optional category_node path segment (e.g., 'computers') and returns ranked items with rank, asin, title, url, price, rating, reviews_count, and image_url. The get_suggestions endpoint takes a prefix string and returns an array of autocomplete suggestion objects, each with a value and type field.
- Track price changes on specific ASINs using
get_product_detailsprice and availability fields - Build category-level bestseller monitors using
get_bestsellerswithcategory_nodefiltering - Aggregate customer sentiment by collecting
body,rating, andverifiedfields fromget_product_reviews - Identify sponsored vs. organic product placement using the
is_sponsoredflag fromsearch_products - Enrich product feeds with
brand,specifications, andimagesdata fromget_product_details - Implement German-language search autocomplete using
get_suggestionsprefix responses - Compare seller and fulfillment details across ASINs using
sold_byandships_fromfromget_seller_info
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Amazon.de have an official developer API?+
How many reviews does `get_product_reviews` return, and can I paginate through all of them?+
total_ratings and overall_rating fields are still returned so you know the full volume even when individual review text is limited. You can fork this API on Parse and revise it to add a dedicated reviews-pagination endpoint if your use case requires more complete review coverage.Can I filter `search_products` results by price range or product category?+
rh parameter, which accepts Amazon's native filter string format (e.g., category node IDs, price range tokens). Be aware that some rh values can trigger upstream 503 errors from Amazon's German storefront, so error handling on that parameter is recommended.Does the API return third-party seller listings or only the featured offer?+
get_seller_info returns the main offer for an ASIN — the sold_by, ships_from, price, and availability of the featured buy-box offer. It does not enumerate all competing seller offers for an ASIN. You can fork this API on Parse and revise it to add a multi-offer listing endpoint that surfaces the full seller list.Are there known reliability issues with any endpoints?+
search_products is the most likely endpoint to encounter upstream 503 errors, particularly when using certain rh filter values or requesting higher page numbers. This is a limitation of Amazon.de's own responses and not specific to any particular query format. Building retry logic into your client is advisable for paginated or heavily filtered searches.