# Product Data Extractor: JSON-LD Prices & Offers (`burnzzz/product-data-extractor`) Actor

Extract published Product JSON-LD from public HTML pages. Preserve prices, currencies, availability, identifiers and offer structures without AI inference. Supports nested graphs and variants; reports missing or invalid metadata explicitly.

- **URL**: https://apify.com/burnzzz/product-data-extractor.md
- **Developed by:** [burnzzz Tools](https://apify.com/burnzzz) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 reports

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Product Data Extractor

Get structured product records from the JSON-LD already published in public HTML pages. Use the output for catalog enrichment, feed preparation, price research, and checking the metadata your storefront exposes to machines.

#### Start a run

Supply one to ten public HTML product URLs in `pageUrls`. No account credentials, paid model, or proxy is required. The Actor fetches each supplied page once, follows bounded redirects, and inspects `application/ld+json` scripts. It does not crawl an entire store or execute JavaScript.

#### Output

One dataset report per successfully fetched and parsed HTML page includes `pageUrl`, `finalUrl`, `status`, `productCount`, `jsonLdBlocks`, `products`, and parser warnings. Product objects preserve published identifiers, name, SKU, brand, descriptions, images, category, offers, and aggregate rating where supplied.

Nested `@graph`, product variants inside groups, arrays, and full schema.org Product type URLs are recognized. Identical Product objects are deduplicated within a page. Offers retain their original structure, including variant-specific prices, currencies, availability, and aggregate price ranges; the Actor does not invent one representative price or imply that structured metadata matches checkout.

A page with no Product JSON-LD produces `no_product_jsonld` with an empty product array. Invalid JSON-LD blocks produce warnings while other valid blocks are still processed. HTTP failures and structural-limit errors appear in the `DIAGNOSTICS` key-value record and do not produce successful page reports. `DELIVERY` identifies spending-limit interruptions and source failures.

#### Pricing

Launch price: $0.005 per completed page report, plus $0.005 per start at 256 MiB. Platform usage is included. A report containing no products is still billable: it records the completed metadata check. Failed fetches do not incur report charges; the start charge still applies. The price displayed before your run is authoritative.

#### Scope and limits

Up to ten pages per run, 200 product objects per page, 2 MiB compressed and decompressed response size, and a bounded request deadline. Public HTTP(S) on ports 80/443 only. Private destinations, credential-bearing URLs, oversized payloads and excessive redirects are rejected. UTF-8 HTML is supported; other character encodings may require preprocessing.

JavaScript rendering, microdata/RDFa, cookie/login flows, browser challenges, hidden APIs, JSON-LD context fetching, `@id` reference resolution, and verification against checkout are not supported. Sites may reject requests; this Actor does not bypass their safeguards. Missing prices remain missing. Relative URLs remain as published.

#### Support

Use the Actor Issues tab and provide a public URL and run ID. Exclude credentials, customer records, and private data. This is an independent utility, not affiliated with retailers or schema.org. Only access sources you are entitled to use.

Schema reference: [schema.org Product](https://schema.org/Product).

# Actor input Schema

## `pageUrls` (type: `array`):

Public HTTP(S) URLs. One to ten HTML product pages.

## Actor input object example

```json
{
  "pageUrls": [
    "https://www.allbirds.com/products/mens-tree-runners-mist"
  ]
}
```

# Actor output Schema

## `reports` (type: `string`):

No description

## `diagnostics` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "pageUrls": [
        "https://www.allbirds.com/products/mens-tree-runners-mist"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("burnzzz/product-data-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "pageUrls": ["https://www.allbirds.com/products/mens-tree-runners-mist"] }

# Run the Actor and wait for it to finish
run = client.actor("burnzzz/product-data-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "pageUrls": [
    "https://www.allbirds.com/products/mens-tree-runners-mist"
  ]
}' |
apify call burnzzz/product-data-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,burnzzz/product-data-extractor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/degRWZnTw8JXKQT74/builds/1dHo7YnHq8i3Y4N0p/openapi.json