News

Changes in Icecat JSON File Structure (Pull-API)

From the 2th of June, the structure of the Icecat JSON files in our Pull-API (API-out) will be changed slightly. The impact of this update is very low.

Currently, we may have for the same tag sometimes an object and sometimes an array depending on if there is data for the object or not. An empty array is used when there is no data in the object, but when there is data it’s represented by an object. You can see an example below regarding ProductFamily tag:

Empty object: 
"GeneralInfo": {       
            "ProductFamily": [],       
            "ProductSeries": {         
           "SeriesID": "1"       
       }    
   }
Populated object:
"GeneralInfo": {     
        "ProductFamily": {         
                "ProductFamilyID": "67439",         
                "Value": "OMEN",         
                "Language": "EN"    
           },    
        "ProductSeries": {         
                "SeriesID": "5821",         
               "Value": "880",         
              "Language": "EN"    
          } 
    }

In the new structure, we will always publish an object’s array, even when it is an empty one without data. The situation with data populated objects will stay as it is right now:

 "GeneralInfo": {       
            "ProductFamily": {},       
            "ProductSeries": {         
           "SeriesID": "1"       
       }    
   }
 "GeneralInfo": {     
        "ProductFamily": {         
                "ProductFamilyID": "67439",         
                "Value": "OMEN",         
                "Language": "EN"    
           },    
        "ProductSeries": {         
                "SeriesID": "5821",         
               "Value": "880",         
              "Language": "EN"    
          } 
    } 

For some entities which are scalar, we are using an array. We will still use an array there even with an empty data set. Example: GTIN.

"GeneralInfo": {     
       "GTIN": [         
                    "08710103824428",         
                    "8710103824428"    
            ] 
     } 

Or:

"GeneralInfo": {     
      "GTIN": [] 
 }
Anastasiia

View Comments

    • Would be an approach. Our dev team: "I think we tried to make that consistent across all methods/calls we have, that's why we had to stick to empty object afair "

  • About time :P

    Getting tired of this:
    [JsonConverter(typeof(SingleOrArrayConverter))]
    public List BulletPoints { get; set; }

    • And, any suggestions for further improvement to make your life easier are welcome.

    • Dear Jos

      We are busy to add this information to the product JSON and XML files. Also we are busy to create separate file OrganizationList.xml for bulk downloads. The development will be finalized in the middle of February. Meanwhile as the temporary solution you can use SupplierList.xml from the reference files. We put "Brand Owner" and "Representative" in the SupplierList.xml under the tag "CustomerService"

      Kind regards

      Vazha Abramishvili

Recent Posts

Shopify Introduces AI Toolkit, Signaling a New Phase in Agentic Commerce

Shopify has introduced a new AI Toolkit for developers, marking another step toward what many…

11 hours ago

BNPL Reaches 50% Adoption in Europe, Reshaping Online Shopping Behavior

According to recent data, 50% of European consumers now use installment or pay-later services, confirming…

1 day ago

Zalando’s Expansion Continues: Bulgaria Launch Expected in 2026

Zalando is continuing its European expansion, with a launch in Bulgaria expected later in 2026.…

2 days ago

Asian Regulators Scrutinize Anthropic’s AI Model as Cybersecurity Risks Rise

Artificial intelligence is moving deeper into critical infrastructure. However, as capabilities increase, so do concerns…

3 days ago

The AI Era: How Autonomous Agents are Redrawing the Roles of POs and Developers

For years, the Agile methodology has relied on a clear boundary: the Product Owner (PO)…

4 days ago

Icecat Release Notes 247: Transparency, Efficiency, and Scalable Foundations

This release brings a combination of data-transparency improvements, operational-efficiency gains, and foundational platform enhancements. We…

1 week ago