If providing data in our preferred format proves difficult for any reason, feel free to send us your catalog data in a format that works best for you.

Using other formats to send Constructor your catalog is only viable for the Proof Schedule. Full integrations require sending catalog data using the catalog management endpoints via HTTPS / FTPS (in the preferred format where applicable).

Constructor's engineers will write custom JavaScript code to extract, analyze, transform, and upload the data in your product catalog files.

Constructor can power a Proof Schedule with catalogs formatted using any of the following file types, as long as the catalog contains the required data fields as defined in the preferred format.

1. .csv - CSV file format - most popular option
2. .json - JSON file format
3. .jsonl - JSONL file format
4. .xml - XML file format

If there is another file format that your team prefers to work with, please don't hesitate to make us aware.

CSV format

When creating CSV files, please use a standard CSV library in the programming language of your choice. The CSV specification is quite detailed, and is more complex than simply separating fields with commas. Some standard libraries we recommend for different languages are:

• Java: Apache Commons CSV
• JavaScript: Papa Parse
• Ruby: CSV
• Python: CSV