Product Information API Get a token

URL-first product data API

Two requests for live product data.

Send a product URL to the stock endpoint when you need availability and offer signals. Send the same URL to the information endpoint when you need a structured product record.

Request API token OpenAPI reference
Stock POST /v1/product-stock
Information POST /v1/product-information
Bulk items[].productUrl
Request 1: stock 200 OK 
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"}'
Request 2: information 200 OK 
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"}'

Current API surface

Choose the endpoint by the job you need done.

The request contract is URL-first. Callers provide productUrl, or items[].productUrl for bulk jobs. Source detection and supplier-specific identifiers 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.
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.
Bulk information POST /v1/product-information/bulk { "items": [{ "productUrl": "https://www.example.com/product/123" }] } Collects product information for batches of product URLs.
Usage GET /v1/usage No request body Returns credits remaining and recent API usage.

Do not send source IDs, external IDs, method names, or cache controls in the request body. Those are internal or response-side details, not caller-provided parameters.

Developer examples

Same input shape, two different outputs.

Use the stock endpoint for availability, offers, price, seller, Prime, and delivery signals. Use the information endpoint for product title, brand, images, attributes, ranks, ratings, and other structured details.

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"}'
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"}'

Product scope

Built for product URLs, not for a single marketplace.

Amazon-related pages can be published as an acquisition cluster, but the homepage should remain the product-wide pillar for supported marketplace and retailer URLs.

URL-first ingestion

Use the product page URL as the stable input instead of asking callers to know source IDs.

Stock and offers

Expose availability, offer count, price, currency, seller, Prime, and delivery-day fields.

Product records

Return product information in structured JSON for catalog, monitoring, and enrichment jobs.

Bulk batches

Batch many URLs through dedicated stock and information bulk endpoints.

Usage tracking

Check credits remaining and recent outcomes without leaving the API surface.

OpenAPI ready

Generate internal clients from the public OpenAPI document instead of hand-maintaining SDKs.

pSEO architecture

Scale search pages without turning the product into an Amazon-only site.

Astro keeps every future landing page pre-rendered as HTML. Each page can have unique metadata, schema, examples, canonical URLs, and sitemap inclusion without adding SSR cost.

FAQ

Short answers for implementation decisions.

These answers are visible HTML first; structured data can mirror them on future pSEO pages.

Is this only for Amazon?

No. Amazon-related searches are one pSEO acquisition cluster. The product API itself is URL-first and not Amazon-specific.

Which request should I use?

Use /v1/product-stock for availability and offers. Use /v1/product-information for product details.

Can I send products in bulk?

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

How do I authenticate?

Send Authorization: Bearer $PIA_API_TOKEN with each request.

What fields can stock return?

Stock responses can include availability, offer count, offers, price, currency, seller, Prime, and delivery-day fields.

What are the limits?

Coverage is best effort by supported marketplace and product. Polling cadence is client-owned and confirmed during onboarding.

Access

Get a token and start with the two core requests.

Use the OpenAPI document for client generation or send a short access request.

Base URL: https://api.productinformationapi.com
OpenAPI: https://api.productinformationapi.com/openapi.json
Request token