Amazon Seller Profiles Scraper

Extract one public Amazon seller profile per run from a seller ID or profile URL. Get seller identity, storefront links, available feedback figures and public business details for seller research or enrichment, then export the dataset as CSV, JSON or Excel.

The Actor supports amazon.com, amazon.co.uk and amazon.de. It does not discover sellers, collect their product catalogs or return private account data. Optional details depend on the page Amazon returns.

Quick start

1. Enter one Seller ID, or clear that field and enter a seller profile URL.
2. Choose the matching marketplace and review the proxy settings.
3. Start the Actor and open the dataset to inspect or export the result.

{
  "sellerId": "A2L77EE7U53NWQ",
  "marketplace": "amazon.com"
}

This requests at most one profile row. Proxy settings default to Residential Apify Proxy. Review the input-field help and the Pricing tab before running. There is no batch input: call the Actor once per seller from your automation.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Export Amazon seller profile by seller ID
• Export Amazon UK seller profile data
• Export Amazon seller profile by URL

What you get

At most one saved seller-profile row per run, with the requested source URL, collection time and available identity, business and feedback fields. A row can contain null fields. The returned storefront link does not represent an extracted seller catalog.

Who is it for?

• Marketplace researchers: Add public seller identity and business details to known seller records.
• Ecommerce teams: Compare separately exported profiles when reviewing reseller presence.
• Automation builders: Enrich one seller at a time for spreadsheets, CRM qualification or BI workflows. Comparisons and alerts belong in your downstream workflow.

How you can use the data

• Enrich one known seller record. Supply its sellerId and matching marketplace, then add available businessName, businessAddress and profile links to your internal review sheet. Missing details remain unknown.
• Review public feedback figures. Keep feedbackPositivePercent and feedbackCountLifetime with sourceUrl and scrapedAt. The feedback periods are not independently verified, despite the legacy count field name.
• Compare separate profile exports. Collect one seller per run, then compare the saved fields in your own spreadsheet. Multiple sellers require separate runs, and the Actor does not discover sellers, certify them or detect changes automatically.

Input settings

Setting	JSON key	Purpose
Seller ID	sellerId	One seller ID. Takes precedence over the URL if both are supplied.
Seller profile URL	sellerUrl	Used when Seller ID is empty. Prefer a seller profile page.
Amazon marketplace	marketplace	amazon.com (default), amazon.co.uk or amazon.de. Match it to a supplied URL.
Proxy configuration	proxyConfiguration	Residential proxy by default. Other supported settings are available in the input editor.

Provide an ID or URL. Neither alternative is individually required, but a run with neither is rejected. The sample Seller ID in the form is a prefill, not an API default: clear it before using the URL field. Detailed connection behavior and limitations are in the input-field help.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Illustrative shape only, not a newly measured seller record. Nullable values show that details are not guaranteed.

{
  "rowType": "sellerProfile",
  "sellerId": "A2L77EE7U53NWQ",
  "marketplace": "amazon.com",
  "sellerName": null,
  "sellerProfileUrl": "https://www.amazon.com/sp?seller=A2L77EE7U53NWQ&language=en_US&currency=USD",
  "storefrontUrl": "https://www.amazon.com/s?me=A2L77EE7U53NWQ",
  "feedbackPositivePercent": null,
  "feedbackCountLifetime": null,
  "businessName": null,
  "businessAddress": null,
  "sourceUrl": "https://www.amazon.com/sp?seller=A2L77EE7U53NWQ&language=en_US&currency=USD",
  "scrapedAt": "2026-10-24T00:00:00.000Z",
  "diagnostics": []
}

Output fields

Field	Meaning
rowType	Always sellerProfile.
sellerId	Identifier found in the URL or returned page, otherwise null.
marketplace	Selected marketplace. Not inferred from a supplied URL.
sellerName	Best-effort seller name from the public page.
sellerProfileUrl	Requested URL. Supplied URLs are not converted to profile URLs.
storefrontUrl	Catalog link constructed from the seller ID and selected marketplace, otherwise null.
feedbackPositivePercent	Detected positive-feedback percentage. The period is not separately identified.
feedbackCountLifetime	Detected rating count. Despite its legacy name, a lifetime period is not independently verified.
businessName	Public business name when detected.
businessAddress	Public business address when detected.
sourceUrl	Requested source URL.
scrapedAt	ISO timestamp when the row was created.
diagnostics	Currently an empty array. Not a per-field completeness report.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing: start is a one-time run-start charge, and seller-profile is charged for a profile row saved to the dataset, with at most one row per run. There are no paid error/status rows.

Invalid input or an unavailable seller does not guarantee that the start charge is avoided. Review platform proxy charges and set an appropriate run spending limit in your client.

See the live Pricing tab for current rates and tier discounts.

Tips for best results

• Prefer a seller profile page or seller ID. A storefront or catalog URL is fetched as supplied and may lack profile details.
• Match the marketplace to the seller URL. The selected marketplace is not inferred from the URL.
• Clear the form's sample seller ID when using a URL. A supplied seller ID takes precedence over the URL field.
• Keep source and collection time in your review sheet. Treat missing business or feedback fields as unknown and verify important details at the source.

Limits and caveats

Only public information is collected. No Amazon login, cookies, order history or private seller-account data is accessed.

A saved profile can have missing fields and does not guarantee every business or feedback value was available. Feedback periods are not independently verified. The currently empty diagnostics array is not a per-field completeness report.

Amazon security responses, localization or page changes can prevent extraction. A run that cannot produce a profile currently fails without a profile row. This does not prove the seller is private or deleted.

There is no seller search discovery, product-listing export, review-text or contact-email extraction, sorting or built-in change detection. Each run accepts one seller, so comparisons across sellers require separate exports.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~amazon-seller-profiles-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "sellerId": "A2L77EE7U53NWQ",
  "marketplace": "amazon.com"
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/amazon-seller-profiles-scraper').call({
  "sellerId": "A2L77EE7U53NWQ",
  "marketplace": "amazon.com"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/amazon-seller-profiles-scraper').call(run_input={'sellerId': 'A2L77EE7U53NWQ', 'marketplace': 'amazon.com'})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Amazon Seller Profiles Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Amazon Seller Profiles Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/amazon-seller-profiles-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Amazon Seller Profiles Scraper by Fetch Cat, or give it the identifier fetch_cat/amazon-seller-profiles-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Amazon Seller Profiles Scraper to retrieve one public profile for seller A2L77EE7U53NWQ on amazon.com. Show available seller and business names, the profile link and collection time, marking missing details.”
• “Collect the single seller profile at the public Amazon profile URL I provide, using the matching marketplace and clearing any sample seller ID. Show available business address and feedback figures without assuming their reporting periods.”
• “Retrieve this one known Amazon seller profile. Keep the original source URL and collection time, then compare the returned fields with the previous profile row I provide as a separate analysis.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Where do I find an Amazon seller profile link or ID?

Open a public seller profile from a product's seller link. The seller query parameter in a profile URL is the seller ID. Supply that ID, or paste the profile URL after clearing Seller ID.

Can I export seller profiles through an API?

Yes. Use the Apify API example above and export the resulting dataset as JSON, CSV or Excel. This is public-page extraction, not Amazon's official seller-account API.

Why are fields null, or why did the run return no profile?

The returned page may omit details, use an unsupported layout or present a security response. Check that the ID exists in the selected marketplace and prefer a profile URL. A failure alone does not establish privacy or deletion.

Does it collect seller products or feedback comments?

No. It returns one profile with available feedback figures, not product catalogs or individual feedback text. See the related product and review Actors for adjacent workflows.

Does it require an Amazon account?

No. It reads public pages without Amazon account credentials. Apify authentication is required for API calls.

Related Actors

More Amazon scrapers

• Amazon Reviews Scraper — Collect product reviews.
• Amazon Products & Search Scraper — Research product search results.

• Amazon Bestsellers Scraper — Explore popular products.
• Walmart Products Scraper — Research another retail marketplace.
• Alibaba Products & Suppliers Scraper — Research wholesale products and suppliers.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥