Skip to content
ParseShelf
Local converter · optional live preview

Free Amazon URL to JSON Converter

Extract ASIN and URL fields instantly. Add live product details with a free preview when you need them.

Live URL to JSON

Convert one Amazon URL to live JSON.

Paste an Amazon product URL. Copy or download the structured response without creating an account.

Try an example
No accountUp to 5 rows

Ready for your input.

Your live Amazon JSON will appear here.Run the preview to see current data from your input.
Local URL → JSON

Normalize an Amazon product URL locally.

Extract the ASIN, marketplace and canonical product URL in your browser. No network, account or parser capacity is needed for this first step.

Browser-only normalizerProduct URL → canonical JSON
1Paste URL2Run3Copy JSON

Local output contains identity and canonical URL fields. Live title, price and ratings appear in the preview below.

Enter an Amazon product URL to create local JSON.
More about Amazon parser fields, API access and workflows
Amazon product URL → JSON

URL fields first. Live product fields when you need them.

The local converter extracts an ASIN, marketplace and canonical product URL without a network request. Start the optional live preview to fetch the title, price, rating and other fields Amazon renders.

StepWhat ParseShelf returnsWhy it matters
Convert a product URL locallyasin, marketplace and canonical product_urlThese fields come from the URL; a price or title cannot be inferred from a link.
Inspect the live JSONtitle, brand, price, rating, reviews_count and availabilityCheck the actual fields before deciding whether the data is usable.
Continue to a full jobJSONL, CSV, XLSX or Markdown from the same normalized row contractScale from one product check to ASIN enrichment, catalog QA or recurring exports.
API example

Use the same Amazon URL in the API.

This example shows the exact shape a developer can use to create a ParseShelf Amazon job. Operators can run the same workflow in the web dashboard, inspect live rows, and download files without writing code.

Use product_url_list when the seed is a product url list. Use full_product when you need product page fields such as brand, bullets, stock text, shipping information, variants, media and review signals. Use listing_only for fast discovery scans before enriching selected ASINs.

Every completed job exposes the same normalized contract across API responses, JSONL exports, CSV files, Excel workbooks and Markdown reports, so downstream systems do not need a separate parser for each Amazon page type.

curl requestPOST /api/v1/jobs
curl -X POST https://parseshelf.com/api/v1/jobs \
  -H "Authorization: Bearer $PARSESHELF_KEY" \
  -H "Content-Type: application/json" \
  -d '{"marketplace": "amazon", "input_type": "product_url_list", "input_value": "https://www.amazon.com/dp/B0060OUV5Y", "mode": "full_product", "target_count": 20}'
sample responseJSON
{
  "schema_version": "1.0",
  "status": "succeeded",
  "outcome": "full",
  "has_failures": false,
  "marketplace": "amazon",
  "input_type": "product_url_list",
  "mode": "full_product",
  "delivered_records": 1,
  "records_delivered": 1,
  "records_failed": 0,
  "charged_units": 5,
  "sample": {
    "asin": "B0060OUV5Y",
    "title": "La Roche-Posay Cicaplast Balm B5 Cream",
    "brand": "La Roche-Posay",
    "price": 18.99,
    "currency": "USD",
    "stock_status": "in_stock",
    "stock_text": "In Stock",
    "rating": 4.7,
    "reviews_count": 20743,
    "product_url": "https://www.amazon.com/dp/B0060OUV5Y"
  },
  "exports": {
    "jsonl": "/api/v1/jobs/{job_id}/download/jsonl",
    "csv": "/api/v1/jobs/{job_id}/download/csv",
    "xlsx": "/api/v1/jobs/{job_id}/download/xlsx",
    "md": "/api/v1/jobs/{job_id}/download/md"
  }
}
Schema

Fields this API returns.

asin

Normalized `asin` field in JSONL, CSV, XLSX and Markdown exports.

title

Normalized `title` field in JSONL, CSV, XLSX and Markdown exports.

brand

Normalized `brand` field in JSONL, CSV, XLSX and Markdown exports.

price

Normalized `price` field in JSONL, CSV, XLSX and Markdown exports.

rating

Normalized `rating` field in JSONL, CSV, XLSX and Markdown exports.

reviews_count

Normalized `reviews_count` field in JSONL, CSV, XLSX and Markdown exports.

stock_text

Normalized `stock_text` field in JSONL, CSV, XLSX and Markdown exports.

product_url

Normalized `product_url` field in JSONL, CSV, XLSX and Markdown exports.

Use cases

Research, monitor and export.

API prototyping

Use Free Amazon URL to JSON Converter for api prototyping with live job progress and downloadable files.

Product validation

Use Free Amazon URL to JSON Converter for product validation with live job progress and downloadable files.

Catalog enrichment

Use Free Amazon URL to JSON Converter for catalog enrichment with live job progress and downloadable files.

Data quality checks

Use Free Amazon URL to JSON Converter for data quality checks with live job progress and downloadable files.

Related pages

More Amazon data workflows.

Practical workflow guide

Amazon Search URL to JSON for Agency Product Data Workflows

When an agency prepares an Amazon report, the first question is often not “How quickly can we export this?” It is “Can this input produce rows that are clear enough to review and use?”

A simple QA workflow helps analysts answer that before they build a larger deliverable.

1. Start with the smallest useful input

Use one representative Amazon search, category, or product URL. If the client has a short list instead, prepare up to 20 ASINs.

Choose an input that reflects the actual assignment. For example:

Example: If the client wants a category review, use the category URL the analyst expects to report on. If the assignment concerns a defined product set, use the corresponding ASIN list.

Keep the original input with the project notes. That makes it easier to explain what was reviewed and to repeat the check later.

2. Preview before committing to the workflow

Open the public preview and inspect up to five live rows before creating an account. The preview does not require a payment card, so it can serve as an initial data-quality checkpoint.

Do not treat five rows as the complete output. Treat them as a quick sample for questions such as:

  • Are the returned rows recognizable as the products the client intended to review?
  • Are the visible values usable for the report’s next step?
  • Which values are present, and which are missing?
  • Does the input appear specific enough for the assignment?

Example: If the preview contains five rows but an important value is missing in several of them, record that limitation before building a client-facing table. Do not silently replace missing values with assumptions.

3. Review observed values, coverage, and missing data

For catalog QA and agency reporting, the presence of a row is only one part of the review. Inspect the observed values and note where coverage is incomplete.

A useful review record can include:

  • The source URL or ASIN list.
  • The date of the review.
  • The number of preview rows inspected.
  • Fields that were populated consistently.
  • Fields with missing or inconsistent values.
  • Any decision to exclude, flag, or manually verify a row.

Market Intelligence labels observed values, coverage, and missing data rather than presenting estimates as exact totals. Use those labels as QA signals. They help distinguish what was observed in the workflow from what an analyst may still need to verify or explain in the report.

Coverage is not a reason to fill gaps with guessed values. A missing value should remain visible as missing, be flagged for follow-up, or be handled according to the agency’s documented reporting rules.

4. Choose the export for the downstream team

Once the preview is acceptable for the next stage, select the format that matches the agency’s workflow:

  • CSV: useful for spreadsheet review, filtering, and handoffs.
  • XLSX: useful when the team needs a workbook-based review process.
  • JSONL: useful when each product row needs to remain a separate structured record.
  • Markdown: useful for a readable review document or internal notes.

The format should follow the handoff, not drive the QA decision. First confirm that the rows and values are appropriate to inspect. Then choose the export that makes the next action easiest.

For repeatable agency work, keep a small mapping note alongside the export. Record which output fields feed the client report, which fields are used for internal QA, and which missing values require review. This reduces confusion when different analysts work on the same account.

5. Repeat the same check on the actual sample

After reviewing the public preview, run the same concrete input through the existing ParseShelf tool. Compare the exported rows with the preview observations and preserve the data-quality notes.

A practical handoff might contain:

  • the original Amazon URL or ASIN list;
  • the selected export format;
  • the exported product rows;
  • a short list of observed coverage or missing-value issues;
  • questions for the analyst or client where manual verification is still needed.

This creates a lightweight path from client input to reviewable product data without requiring the analyst to manually collect every row first.

Try the agency sample workflow

ParseShelf is an existing public tool for this workflow. The sample workflow accepts one Amazon URL or up to 20 ASINs, lets a visitor preview up to five live rows before creating an account, and supports CSV, XLSX, JSONL, or Markdown exports for completed jobs.

Want to judge the output with a concrete sample? Send one Amazon URL or up to 20 ASINs, and request a clean sample with CSV included among the available formats. Run the Amazon URL-to-JSON workflow.

FAQ

Free Amazon URL to JSON Converter questions.

Does this converter fetch live Amazon product data?
The live preview collects available product fields from your URL. The separate local normalizer extracts only the ASIN, marketplace and canonical URL without contacting Amazon.
What is included in the free URL-to-JSON result?
The local tool extracts the ASIN, marketplace and canonical product URL. It runs in your browser. Product title, price and ratings require the separate live preview.
How do I get a complete product export?
Continue with the same URL in the live preview. After checking the available rows, sign in to create a job and download CSV, XLSX, JSONL or Markdown.