Content Syndication


Thanks to the different endpoints listing in this use case, you can explore and syndicate data from the highest level (catalogs) to the lowest level (part number).

Navigation in the data structure

The data featured in the TraceParts API are associated with the required language.
If data do not exist in the required language, their value is returned in the default language chosen by the supplier.

For example, if you wish to use the API for your application in Spanish, simply ask for the data in Spanish.
If the requested language is not available for all the data, TraceParts will manage the data according to the supplier’s choices.

To fetch the information, you can explore it from the list of catalogs associated with your API key (catalogList) to retrieve the classification structure for each one using categoryList enpoint and continue for the products with the productList endpoint.

At the end, for each product, you get the list of associated part number, with the partNumberList endpoint, associated to the CAD model availability. If this value is set to "true", it means at least one CAD format can be provided for the related part number.

Data indexing

These data can also be mass indexed with the same information as previously mentioned.

The catalogList and productList endpoints provide an update date. By storing this "updateDate" timestamp in your system, you can check if any data has changed since your last call. At the top level, for the catalogList endpoint, the "updateDate" value changes if any of the sub-levels (categories or products) has any change. It means, if you "updateDate" is the same as in your system, you do not need to go further in the syndication because any sub-level remains unchanged.

The previous case about the catalogList also works the same way for the productList.

Developer support

Please contact us for any problem, question or comment related to this content integration.