Open a screenshot to inspect the actual path from input to output and observed intelligence.
Preview 5 rows free
Input → live rowsA visitor can test one URL or up to 20 ASINs before signing in.
Inspect output
Rows → exportsInspect the columns before choosing your export.
Explore signals
Market IntelligenceCompare observed prices and spot changes over time.
Guide
How to use this ParseShelf resource.
Why test in Postman
Postman is useful when a developer, analyst or technical founder wants to validate the request body, authentication header and export flow before writing code. It also makes it easy to share a working request inside a team.
Use an environment variable for PARSESHELF_KEY and keep the request body focused on one input type at a time.
Request body
The most important fields are marketplace, input_type, input_value, mode and target_count. The examples use product_url_list for one product, but the same endpoint also accepts search_url, category_url and asin_list.
If a request works in Postman but fails in production, compare headers, JSON escaping and environment variables first.
After creation
Copy the returned job ID into the status and download requests. Poll until the job reaches succeeded, then download JSONL, CSV, XLSX or Markdown.
This mirrors the production integration and helps a team understand the whole lifecycle, not just the create request.
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.