How to Export an Amazon ASIN List

Option 1: Exporting Reports from Seller Central

Seller Central can export your own active ASINs through inventory and listing reports. The fields cover SKU, ASIN, title, price and available quantity. The data is authoritative, completely free and needs no technical work at all. The catch is scope: it covers your own catalogue only, so competitor and category products are out of reach.

Field depth matters just as much. Back-office reports carry the operational fields you need to run a store, but no BSR rank, competitor price or search-result position. If you only need to know which ASINs you own, reports are enough. If you need product research, competitor tracking or category analysis, they are not.

• Good for: auditing your own listings, checking inventory and pricing, acting as internal master data
• Not suitable for: competitor ASINs, full category coverage, cross-marketplace rollups, market-side fields

Option 2: Collecting from Bestseller Pages by Hand

Bestseller and New Releases pages carry the category node ID in the URL. In a link such as https://www.amazon.com/Best-Sellers-Baby-Baby-Care-Products/zgbs/baby-products/17720255011/, the trailing 17720255011 is the node ID. Extract it once and you can revisit the same chart whenever you like.

Copying titles or links page by page is how most teams start. A single category can run to dozens of pages with dozens of products each, so manual collection is slow, easy to skip rows on, never produces a clean audit trail, and never guarantees that today's snapshot lines up with yesterday's.

This approach only suits a one-off study on a very small sample, such as reviewing the top 50 products in a narrow subcategory. The moment you need a list that is repeatable, comparable across weeks and refreshed daily, you need an interface.

Option 3: Pull a Category ASIN List with the Category Endpoint

addCategory400Task takes a category node ID (nodeId) and collects the ASIN list for that category chart, up to 400 pages. The page parameter is optional, so leaving it out collects all 400 pages of that chart by default.

Submit nodeId=17720255011 with region=us and zipCode=10001, and the finished task returns every ASIN in that chart plus the page, nodeId, region and type fields. The type value is fixed to BSR, marking the data as coming from a category chart rather than a keyword search or a store listing.

The usual next step is to sample a few products for detail, judge the category's competitive structure through its price bands, rating distribution and listing-age spread, and decide whether to go deeper. Because the interface repeats on schedule, you can build a comparable series over time.

• Request: nodeId (required), page (optional, maximum 400), region (required), zipCode (required)
• Response: asins (in page display order), page, nodeId, region, type

Option 4: Export a Store's ASINs with the Seller ASIN Endpoint

addSellerAsinTask takes a seller ID (sellerId) and returns that store's ASINs in page display order, so the earlier an ASIN appears, the more recently it was listed. Omit the page parameter and the task collects the whole store.

That ordering makes the endpoint ideal for new-listing monitoring. Collect the same store's list once a day, diff it against yesterday's, and every new ASIN is a freshly launched product. Instead of refreshing a storefront page by hand, the interface runs unattended and builds a dated launch history.

Paired with addSellerTask you also get the store's ratings, business name and per-star review distribution to judge overall health. A seller whose rating keeps climbing and who launches often usually belongs on your watch list of competitors.

Only Need the Top 100? Use the BSR Chart Endpoint

addBsr100Task accepts the full chart URL including the domain, and type 1 for Best Sellers or type 2 for New Releases. The returned asins array is in rank order, the second page starts at rank 51, and the page field records which page you are reading.

The endpoint also echoes the url you submitted, with query parameters stripped by the server. That echo matters once dozens of chart tasks run at once, because it lets you trace every record back to its source and reconcile the results reliably.

What to Do Once You Have the List

An ASIN list is only the starting point. The usual workflow is to take ASINs from the category, store or chart endpoint, then enrich them through addAsinTask with price, rating, review count, BSR rank, variations and the rest of the 58 available fields.

Note that list and detail endpoints have different cost profiles: list responses are lightweight arrays, while detail responses carry many fields across a much larger payload. Filtering with a list first, then enriching only the products that matter, is therefore the cheaper order of operations.

For continuous competitor monitoring, turn the chain into a daily job: pull the list, diff it to find new products, enrich the details, load your warehouse and publish a dashboard. Every step runs through the interface with no manual work.

• Product research: pull ASINs by category, enrich details, analyse price bands and ratings
• Launch monitoring: pull store ASINs daily, diff for new items, enrich to gauge potential

FAQ