Because of the size of index files, it is in many cases advised to use real-time data requests. This simplifies the import of Icecat data, as there’s no need for first matching your catalog with Icecat’s very large index files. Especially, in case of smaller, focussed catalogs, it’s more efficient to use the real-time method. A prerequisite is that your catalog contains product identifiers, such as Brand+Part Code, and/or GTIN (EAN, UPC).
If you decide to use – or switch your interface to – real-time Icecat Data requests, you effectively bypass the (very large) index files. In your requests you only need to download data that is present in your product catalog, and therefore this method is very efficient. We would advise to always evaluate the real-time method first, as it will avoid downloading the very large index files.
The description below is based on section 2.2. of the Icecat XML manual: https://iceclog.com/wp-content/uploads/2018/12/Open-Catalog-Interface.pdf
Examples links, if you need to get an xml file of product ‘Compaq 6710b Base Model Notebook PC’. Manufactured by HP, with part number RJ459AV, in English, the call will be:
In case you want to retrieve data on the basis of a GTIN code (EAN or UPC).
An example of the English standardized version of Canon 1447B006:
The general format of the call is:
https://data.Icecat.biz/xml_s3/xml_server3.cgi?prod_id=<product code brand>;brand=<brand name>;lang=<language code>;output=<output>
https://data.Icecat.biz/xml_s3/xml_server3.cgi?ean_upc=<GTIN code>;lang=<language code>;output=<output>
Where: prod_id: the manufacturer product code of the requested product, brand: name of the manufacturer or brand of the requested product, ean_upc: the EAN or UPC code to identify a product, lang: the language or locale code like EN, NL, FR, DE-CH, see the complete language/locale table, output: the type of response. It can be productxml (the product XML file), productcsv (the product CSV file), richproductcsv (for rich media assets associated to the product) and metaxml (the index or meta information on the Brand + ProdID/M_Prod_ID or EAN/UPC).
For more information on real-time CSV access see the Icecat CSV manual, which is a variant of the calls above.
If you call by Icecat ID, the most efficient calls are in case of Open Icecat:
or in case of Full Icecat subscriptions:
Where “en” can be replaced by any language/locale code. And 29627732 is de unique Icecat ID for a product. Icecat IDs are retrieved from the Icecat index files, as explained in the complete XML documentation.
Also the xml_s3 service can be used, but is slightly less efficient:
https://data.Icecat.biz/xml_s3/xml_server3.cgi?product_id=<Icecat product code>;lang=<language code>;output=<output>
Take care that in case of Full Icecat, your IP addresses from where you request data are listed in your user profile. Use the Icecat access credentials that you receive upon (free) registration.
You have data access depending on your subscription: Open Icecat versus Full Icecat, Data versus URL, and the languages or locales to which you are authorized.
Read further: Manuals, CSV, icecat data, real-time access, XML
Hello, which is the best method to collect all products id? We have many different between https://data.icecat.biz/export/freexml.int/ and https://data.icecat.biz/export/freeurls/
Should not have the same list of products?
Hi Francesco, You should use https://data.icecat.biz/export/freexml.int/. Here, you can find product IDs to all Open Icecat datsheets (the daily index is default) and links to the related XMLs. Product_ID is the Icecat ID, while Prod_ID is the Manufacturer Part Number (MPN) or product code.
Your email address will not be published. Required fields are marked *
This site uses Akismet to reduce spam. Learn how your comment data is processed.