Store catalogue to CSV.
Export a supported store's catalogue: your agent or the dashboard runs the store's search endpoint as an extraction Job, which returns the records as JSON. Download them as a CSV or JSON file from the Job's results on the dashboard, or ask your agent to write the CSV. Supported: brand stores worldwide. A bounded result is not a claim to the merchant's full inventory.
Availability
Extraction Jobs are open to every account, starting with 200 free trial credits. For a store that is not listed, request it.
How scope works
One Job covers one URL. A store URL starts at its catalogue; a collection or search URL narrows it. The defaults are deliberately small.
| Control | What it changes | Practical check |
|---|---|---|
max_pages (1–10, default 1) | Listing pages the Job may read | Raise it only if the first page shows a meaningful continuation. |
max_products (1–250, default 50) | Upper bound on returned products | Large catalogues need several narrower collection URLs. |
| Product details Job | One product URL with all its reported variants | Use it when the listing record lacks fields you need. |
Check the file before importing it
- Check the Job status and record count, and read any errors or partial-result notes.
- Check a sample product against its source URL and retrieval time.
- Keep product and variant identifiers as separate columns; do not use titles as stable keys.
- Prices stay in the source's units; currency is not inferred. Store the file and its Job ID in your own system, since results expire after seven days.
Download a synthetic catalog CSV to inspect the column layout. Every row is fictional; the file has no source URL, retrieval time or live offer values.