Product URL API

Product URL API for simple product inputs

Keep client integrations focused on product page URLs. The API resolves supported targets internally and returns stock or product information responses.

Product page URLhttps://shop.example/p/123
StockPOST /v1/product-stock

Use stock when availability, offers, price, seller, and delivery signals drive the workflow.

Request body
{
  "productUrl": "https://shop.example/p/123"
}
Response preview
{
  "externalId": "B0EXAMPLE1",
  "source": "amazon_gb",
  "method": "checkStock",
  "outcome": "OK",
  "inStock": true,
  "offerCount": 2,
  "offers": [
    {
      "price": 49.95,
      "currency": "GBP",
      "seller": "AquaPro",
      "fulfilment": "FBA",
      "deliveryDays": 2
    },
    {
      "price": 54.99,
      "currency": "GBP",
      "seller": "PartsHub",
      "fulfilment": "FBM",
      "deliveryDays": 4
    }
  ],
  "cacheStatus": "live",
  "creditsRemaining": 4871
}
inStockofferCountpricesellerdeliveryDays

Request shape and public routes.

Single requests send productUrl. Bulk requests send items[].productUrl. Bearer auth is required for product and usage routes.

Use caseEndpointRequest bodyReturns
Check stockPOST /v1/product-stock{ "productUrl": "https://shop.example/p/123" }Returns availability, offer count, price, currency, seller, fulfilment, and delivery fields for one product page URL.
Get product informationPOST /v1/product-information{ "productUrl": "https://shop.example/p/123" }Returns title, brand, images, attributes, ratings, category data, and other product details for one product page URL.

Run it with curl, Node.js, or Python.

Put your API token in PIA_API_TOKEN, replace the example URL with a product page from a supported store, and run the snippet. API tokens are in your account console.

Errors return error.code, error.message, error.requestId, and error.retryable. When retryable is true, wait for the Retry-After seconds, then send the request again. Only successful requests use credits.

The OpenAPI reference lists every field and status code.

POST /v1/product-stock
Shell
curl -sS https://api.productinformationapi.com/v1/product-stock \
  -H "Authorization: Bearer $PIA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"productUrl": "https://shop.example/p/123"}'

Fields this workflow usually reads.

Exact fields depend on the endpoint, the product page, and the store's coverage.

productUrlinStockofferCountproductInformationcreditsRemaining

Where this page fits.

Typical jobs teams build on these endpoints.

Product add flows

Let users submit a product page URL and choose stock or information enrichment.

Marketplace abstraction

Keep request bodies consistent across supported retailer and marketplace URLs.

Supplier-key derivation

Leave supported source and product-key resolution to the API.

Integration simplification

Avoid asking callers to maintain marketplace-specific request parameters.

Coverage and operating boundaries.

Coverage is enabled by supported retailer, marketplace, and product page URL.

Polling cadence belongs to the client integration and is discussed during onboarding.

The API is not an official marketplace partner API and does not promise unlimited collection.

Short answers for evaluation.

Answers to the questions teams ask before they integrate.

Do callers provide marketplace IDs or supplier IDs?

No. Callers send productUrl for single requests or items[].productUrl for bulk requests. Internal identifiers are derived by the API when the URL is supported.

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 page URLs and return per-item results.

How is coverage confirmed?

Share target retailers or marketplaces, expected volume, required fields, and sample product URLs during onboarding.