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

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

Pricing

$8.00 / 1,000 product data sheet returneds

Go to Apify Store
EAN GTIN Product Data API - Icecat Specs, Images, Descriptions

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

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.

Pricing

$8.00 / 1,000 product data sheet returneds

Rating

0.0

(0)

Developer

Nabeel Hassan

Nabeel Hassan

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

6 days ago

Last modified

Share

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

{
"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.