Amazon acquisition cluster

Amazon scraping API for product URL workflows

Use Amazon product URLs with the same URL-first contract used across supported marketplaces. Stock and product information remain separate API jobs.

/v1/product-stock request
curl -sS https://api.productinformationapi.com/v1/product-stock \
  -H "Authorization: Bearer $PIA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"productUrl":"https://www.amazon.co.uk/dp/B0EXAMPLE1"}'

Which endpoint do I use?

Public callers send productUrl, or items[].productUrl for bulk requests. Source, supplier key, and method metadata are derived by the API.

Use case Endpoint Request body Returns
Stock check POST /v1/product-stock { "productUrl": "https://www.example.com/product/123" } Checks live availability, offer count, price, seller, Prime, and delivery signals for one product URL.
Product information POST /v1/product-information { "productUrl": "https://www.example.com/product/123" } Returns a structured product snapshot such as title, brand, images, attributes, ratings, and ranks.
Usage GET /v1/usage No request body Returns credits remaining and recent API usage.

Do not send caller-provided source, externalId, or method values. Those fields may appear only as derived response metadata.

Fields this workflow usually reads.

The exact response depends on the endpoint, product URL, and source coverage, but these are the fields this page is designed around.

inStockofferCountoffers[]productInformationcreditsRemaining

Amazon product checks

Use the URL-first API contract to keep this workflow tied to product URLs instead of marketplace-specific request parameters.

Availability monitoring

Use the URL-first API contract to keep this workflow tied to product URLs instead of marketplace-specific request parameters.

Product data enrichment

Use the URL-first API contract to keep this workflow tied to product URLs instead of marketplace-specific request parameters.

Offer review

Use the URL-first API contract to keep this workflow tied to product URLs instead of marketplace-specific request parameters.

Coverage is best effort by supported marketplace, retailer, and product URL.

Polling cadence is owned by the client integration.

The API does not claim official marketplace affiliation or unlimited scraping.

Is Product Information API an official Amazon API?

No. It is a product data API that can support Amazon-related workflows where coverage is enabled.

Do I need to send an ASIN?

No. Send the Amazon product URL. The API derives supplier keys internally when the URL is supported.

Can I scrape Amazon stock and product information separately?

Yes. Use the stock endpoint for availability and offers, and the information endpoint for product metadata.

Can I send Amazon URLs in bulk?

Yes. Use the bulk stock or bulk information endpoint with items[].productUrl.