Product stock API

Product stock API for live availability checks

Submit a product URL and receive stock-oriented signals such as inStock, offerCount, price, currency, seller, Prime, and delivery days.

Request API token OpenAPI reference

/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.example.com/product/123"}'

Endpoint map

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.
Bulk stock	`POST /v1/product-stock/bulk`	`{ "items": [{ "productUrl": "https://www.example.com/product/123" }] }`	Runs stock checks for many product URLs in one request.
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.

Response fields

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[]pricecurrencysellerprimedeliveryDays

Use cases

Availability checks

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

Buy box and offer review

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

Pricing operations

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

Alerting workflows

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

Limitations

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.

FAQ

Is the API tied to one marketplace?

No. The public contract is URL-first and marketplace-neutral. Coverage is confirmed during onboarding.

Do callers provide source IDs or supplier IDs?

No. Callers send productUrl, or items[].productUrl for bulk requests. Source and supplier keys are derived internally.

Which endpoint should I use first?

Use product-stock for availability and offers, and product-information for catalog details.

Can I use bulk requests?

Yes. Dedicated stock and information bulk endpoints accept arrays of product URLs.