# EAN GTIN Product Data API - Icecat Specs, Images, Descriptions (`nabeelbaghoor/ean-gtin-product-data-api`) Actor

Look up product data by EAN, GTIN, UPC, MPN or Icecat id through the Icecat JSON API: titles, descriptions, specifications, images, videos, manuals, reasons to buy, reviews, related products and packaging in 80 locales. Bring your own Icecat token. Pay per product.

- **URL**: https://apify.com/nabeelbaghoor/ean-gtin-product-data-api.md
- **Developed by:** [Nabeel Hassan](https://apify.com/nabeelbaghoor) (community)
- **Categories:** E-commerce, Developer tools, Business
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$8.00 / 1,000 product data sheet returneds

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## EAN GTIN Product Data API - Icecat Specs, Images, Descriptions

Turn a list of EANs, UPCs, manufacturer part numbers or Icecat ids into complete product data sheets from the Icecat catalogue.

### What it collects

- **Identity**: title, brand, manufacturer product code, product name, every approved GTIN, category, product family and series, release and end of life dates.
- **Marketing content**: long and short descriptions, bullet points, marketing text, reasons to buy and product stories.
- **Specifications**: feature groups with every technical specification Icecat holds, plus feature logos.
- **Media**: gallery images, videos, PDF manuals, 3D tours and other multimedia objects.
- **Relations and more**: alternatives, accessories, consumables, services and compatible products, reviews, packaging, the brand owner and its representatives, and download popularity.

### Input

- **Products**: one per line. A 12 to 14 digit GTIN (UPC-A, EAN-13, GTIN-14), an Icecat product id, or `Brand | ProductCode` such as `HP | RJ459AV`.
- **How to read each line**: automatic by default. Choose GTIN explicitly for 8 digit EAN-8 codes, which otherwise look like Icecat ids.
- **Language (locale)**: any of the 80 Icecat locale codes, such as EN, DE, FR, ES\_MX or ZH\_TW. The international INT locale is not served by the JSON interface.
- **Sections**: leave empty for the full data sheet, or pick sections for a granular call. Essential info, title, marketing text, packaging, brand organisations and analytics exist only as sections.
- **Related products per relation type**: optional cap on alternatives, accessories and the other relation lists. Icecat defaults to 500 and accepts up to 3000.
- **Icecat username, API access token, content access token**: your own Icecat credentials, stored as secrets.
- **Maximum results** and **requests per minute** bound the run.

### Example output

```json
{
  "requested": "1445",
  "requestedAs": "icecat_id",
  "language": "EN",
  "sections": ["full"],
  "found": true,
  "icecatId": 1445,
  "title": "HP Two-view Cling Film",
  "brand": "HP",
  "productCode": "Q1915A",
  "productName": "Two-view Cling Film",
  "gtins": ["0088698419298", "088698419298"],
  "category": "Printing Films",
  "releaseDate": "01-07-2006",
  "endOfLifeDate": "30-12-2010",
  "retrievedAt": "2026-09-25T09:14:52.118Z",
  "record": { "GeneralInfo": {}, "Image": {}, "Gallery": [], "FeaturesGroups": [], "...": "the whole Icecat data object, unchanged" },
  "statusCode": null,
  "note": null
}
```

### FAQ

#### What is the Icecat product data API used for?

Filling an ecommerce catalogue, a PIM or a marketplace feed with manufacturer approved content. A webshop sends its EAN list and gets back titles, descriptions, specification tables and image URLs for each product. A comparison site pulls specifications across a category. A distributor checks which of its SKUs Icecat covers and in which languages.

#### Do I need an API key?

Yes. This actor is bring-your-own-key and never ships credentials of its own. You need an Icecat account (Open Icecat registration is free) and an API access token from My Icecat, Access Tokens. Put your username and the token in the input, or set them once as the DATA\_API\_USERNAME and DATA\_API\_KEY environment secrets. The token is a UUID and travels as the `api-token` header, as the Icecat manual requires, and it replaces IP whitelisting, which a cloud run cannot use. An optional content access token makes Icecat attach access to every image and multimedia URL in the answer.

#### Which products can I read?

Whatever your Icecat account can read. Open Icecat covers the brands that sponsor open content; Full Icecat covers the whole catalogue for the verticals in your subscription. A product outside your access comes back as its own row with `found: false` and Icecat's own StatusCode, for example 14 for a brand restricted product, and it is not charged.

#### What happens to a product Icecat does not have?

It becomes a row saying so rather than a gap: `found: false`, with a note quoting Icecat's answer, such as "Missing information about product", "The GTIN can not be found" or "Products datasheet is not yet released" for the chosen locale. A run over a thousand EANs therefore tells you exactly which ones Icecat does not cover.

#### Why is the data sheet kept whole under `record`?

Because an Icecat data sheet is deep: feature groups, galleries, multimedia, relations and reviews each have their own structure, and a fixed set of columns would drop most of it. The lifted columns are fields the Icecat manual names, and the complete `data` object sits beside them unchanged.

#### Can this actor change anything in my Icecat account?

No. The Icecat JSON interface has one read route, and that is the only call this actor makes.

#### What does it cost?

Pay per result: one charge per product that comes back with a data sheet. Products Icecat does not return are never charged. Your Icecat subscription is billed separately by Icecat.

### Keyword map

EAN lookup API, GTIN lookup API, UPC product lookup, product data API, product specifications API, Icecat API, Open Icecat, Icecat JSON, product content API, product catalogue data, product images API, product descriptions API, MPN lookup, manufacturer part number lookup, PIM data feed, ecommerce product content, product data sheet, technical specifications by EAN.

# Actor input Schema

## `products` (type: `array`):

One product per line. A 12 to 14 digit GTIN (UPC-A, EAN-13 or GTIN-14), an Icecat product id, or a brand and manufacturer product code written as "Brand | ProductCode", for example "HP | RJ459AV". Icecat serves one product per request, so each line is one call.

## `identifierType` (type: `string`):

Leave on automatic and each line is read by its shape: a line with a | is a brand and product code, 12 to 14 digits is a GTIN, and a shorter number is an Icecat product id. An 8 digit EAN-8 looks like an Icecat id, so choose GTIN explicitly for those.

## `language` (type: `string`):

Icecat locale short code for the content. The international INT locale is not available on the JSON interface. A data sheet not yet released in the chosen locale comes back as its own row saying so.

## `sections` (type: `array`):

Leave empty for the full product data sheet. Pick sections to fetch only those parts, which Icecat calls a granular call. Essential info, title, marketing text, packaging, brand organisations and analytics are only available this way.

## `relationsLimit` (type: `integer`):

How many alternatives, accessories, services, consumables and compatible products to return for each relation type. Icecat uses 500 when this is blank and accepts up to 3000.

## `maxResults` (type: `integer`):

Stop after this many rows. Each row is one product.

## `requestsPerMinute` (type: `integer`):

Pacing ceiling for calls to the Icecat API. Icecat does not publish a rate limit for the JSON interface, so this stays moderate by default. A 429 answer is retried with backoff.

## `username` (type: `string`):

Your Icecat username, sent as the shopname parameter. It is shown at the top of My Profile on icecat.biz. Leave blank to use the DATA\_API\_USERNAME environment secret.

## `apiKey` (type: `string`):

Your own Icecat API access token (My Icecat, Access Tokens), sent as the api-token header. It replaces IP whitelisting, which a cloud run cannot use. This actor is bring-your-own-key and never ships credentials of its own. Leave blank to use the DATA\_API\_KEY environment secret.

## `contentToken` (type: `string`):

Optional. Your Icecat content access token, sent as the content-token header, so Icecat attaches it to every image and multimedia URL in the answer. Leave blank to use the DATA\_API\_CONTENT\_TOKEN environment secret, or to skip it.

## `baseUrl` (type: `string`):

Override the host the actor calls. Only useful for testing against a different environment.

## Actor input object example

```json
{
  "products": [
    "HP | RJ459AV",
    "1445"
  ],
  "identifierType": "auto",
  "language": "EN",
  "maxResults": 100,
  "requestsPerMinute": 60
}
```

# Actor output Schema

## `records` (type: `string`):

One row per requested product, alongside the identifier that produced it.

# 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 = {
    "products": [
        "HP | RJ459AV",
        "1445"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nabeelbaghoor/ean-gtin-product-data-api").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 = { "products": [
        "HP | RJ459AV",
        "1445",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("nabeelbaghoor/ean-gtin-product-data-api").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 '{
  "products": [
    "HP | RJ459AV",
    "1445"
  ]
}' |
apify call nabeelbaghoor/ean-gtin-product-data-api --silent --output-dataset

```

## MCP server setup

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

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/gnr6Ocp6EXVaREmcS/builds/Pk53mW8Zb02wGJKIw/openapi.json