You can now export your catalog data from Constructor using the Tasks API. This gives your team a repeatable, self-serve way to generate an export file on demand and download it once it’s ready.

What’s new

• Create a Catalog Export task and get back a task ID.
• Check status and download the export file once it’s ready.

Why it matters

• Makes it easier to validate your catalog, troubleshoot issues, and share data with downstream systems.
• Gives you a self-serve way to generate exports without needing manual support.

Common customer use cases

• Catalog QA after an ingest change: Export items/variations and compare against your source feed to confirm the right fields are present and updated.
• Troubleshooting unexpected search/browse behavior: Pull an export to spot missing attributes, incorrect values, or out-of-date availability/pricing.
• Downstream processing / audits: Generate a point-in-time export to load into your own tools (data warehouse, scripts, BI) for analysis and reconciliation.
• Taxonomy review (item groups): Export item groups to review hierarchy structure and naming, and to validate updates before broader changes.

How to use it (high level)

• Create an export task → get a task ID.
• Check status until it’s DONE.
• Download the file using the returned URL.

Notes

• Only one export can be queued or running per ac_key at a time.
• Depending on what you’re exporting, you may need to provide both ac_key and section.

Learn more about Catalog Export API