Create a job
Send a POST request to /api/v1/jobs with marketplace set to amazon. Choose input_type based on the source: search_url for Amazon search pages, category_url for category pages, product_url_list for direct product URLs, or asin_list for bulk ASIN enrichment.
Use listing_only when you need discovery rows and ranking positions. Use full_product when you need product page fields such as brand, bullets, images, product details, stock text, shipping information, variants and review signals.
Poll progress
The job status endpoint exposes status, delivered record counts, charged units, speed and export readiness. This lets a script wait for completion without guessing when Amazon data is ready.
The dashboard shows the same lifecycle for non-technical users. That makes ParseShelf easier to roll out because product researchers and developers do not need separate tools.
Download exports
Use the download endpoint when status is succeeded. JSONL is line-oriented for pipelines, CSV is portable for BI tools, XLSX is easiest for spreadsheet users and Markdown helps produce quick internal reports.
All export formats come from the same normalized rows, so a team can inspect a spreadsheet and ship a JSONL pipeline without reconciling two schemas.
Production checklist
Start with one small input and compare the delivered fields with the report, catalog or pipeline you actually need.
Keep the job ID, source URL, mode and run date with downstream exports so operators and developers can audit the same result.