Product data API

Product data API for URL-first integrations

Build product data workflows around URLs instead of marketplace-specific identifiers. Use separate endpoints for stock signals and structured product information.

Request API token OpenAPI reference

/v1/product-information request

curl -sS https://api.productinformationapi.com/v1/product-information \
  -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.
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.

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.

productInformationtitlebrandimagesattributesratingscreditsRemaining

Use cases

Catalog enrichment

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

Offer monitoring

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

Product onboarding

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

Marketplace data checks

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.