Amazon Influencer Storefront Scraper avatar

Amazon Influencer Storefront Scraper

Pricing

Pay per event

Go to Apify Store
Amazon Influencer Storefront Scraper

Amazon Influencer Storefront Scraper

👤 Extract public Amazon creator profiles, idea lists, curations, social links, and recommended ASINs into separate datasets for influencer research.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 days ago

Last modified

Share

Extract public Amazon creator profiles, idea lists, curations, and recommended products from storefront URLs.

Use Amazon Influencer Storefront Scraper to connect a creator identity to the collections and ASINs visible on their public Amazon page. The Actor runs without Amazon login credentials and saves clean profile, collection, and product datasets.

What does Amazon Influencer Storefront Scraper do?

The Actor accepts URLs such as https://www.amazon.com/shop/sydneydelrey. It reads the public storefront and returns:

  • 👤 Creator handle, display name, biography, avatar, marketplace, and social links
  • 📋 Public idea-list titles, IDs, URLs, images, and advertised item counts
  • 🎬 Public curation titles, IDs, URLs, images, and post counts
  • 📦 Visible product ASINs, brands, titles, images, links, and price or availability text
  • 🕒 A scrapedAt timestamp on every record for monitoring and comparison

You can also submit a direct /shop/{handle}/list/{id} URL to target one idea list.

Who is it for?

Influencer marketing agencies

Build creator shortlists, inspect creator-to-product fit, and export storefront evidence for campaign planning.

Amazon brands and marketplace teams

Find which public creators recommend an ASIN, review adjacent brands in the same list, and monitor assortment changes.

Affiliate and partnership managers

Qualify creators from their public biography, social links, list themes, and visible product mix before outreach.

Creator-commerce researchers

Create repeated snapshots for creator economy, category, product placement, or social-commerce analysis.

Developers and data teams

Feed normalized profiles, collections, and ASINs into a warehouse, CRM, dashboard, alert, or enrichment pipeline.

Why use this Amazon influencer scraper?

Manually opening storefronts and copying products is slow and inconsistent. This Actor provides a repeatable public-data workflow:

  • ✅ Batch several storefront URLs in one run
  • ✅ Keep three entity types in separate typed datasets
  • ✅ Deduplicate profiles, collections, and ASINs within a run
  • ✅ Bound collection and product volume for predictable runs
  • ✅ Retry temporary Amazon responses with exponential backoff
  • ✅ Add Apify Proxy settings only when a marketplace needs them
  • ✅ Export JSON, CSV, Excel, XML, RSS, or JSONL from Apify

What data can I extract?

DatasetImportant fieldsTypical use
Creator profileshandle, name, description, avatarUrl, socialLinks, marketplaceCreator qualification and outreach enrichment
CollectionscollectionType, collectionId, title, collectionUrl, itemCountContent-theme and assortment analysis
Productsasin, brand, title, productUrl, imageUrl, priceTextProduct placement, competitor, and campaign research

Fields that Amazon does not show publicly are omitted. For example, priceText is optional because some product cards show availability language instead of a price.

Multiple datasets

The Actor creates three datasets because profiles, collections, and products have different shapes.

  1. Creator profiles use the run's default dataset.
  2. Idea lists and curations use the collections dataset alias.
  3. Recommended products use the products dataset alias.

Open the run's Storage tab to choose and export each dataset. The main run output also links directly to all three. This structure avoids mixed rows and makes downstream schema validation easier.

How to scrape an Amazon influencer storefront

  1. Open the Actor input page.
  2. Add one or more public Amazon /shop/ URLs.
  3. Keep Extract recommended products enabled if ASINs are needed.
  4. Choose a small collection and product limit for the first run.
  5. Click Start.
  6. Review Creator profiles, Collections, and Products in the output.
  7. Export the dataset you need or access it through the API.

A small first run with one creator, three collections, and eight products per list is a useful validation workflow.

Input

{
"startUrls": [
{ "url": "https://www.amazon.com/shop/sydneydelrey" }
],
"scrapeProducts": true,
"maxCollectionsPerStorefront": 3,
"maxProductsPerCollection": 8,
"requestRetries": 2
}

Input fields

FieldTypeDefaultDescription
startUrlsarrayrequiredPublic Amazon storefront or direct idea-list URLs
scrapeProductsbooleantrueFetch visible product cards from selected idea lists
maxCollectionsPerStorefrontinteger5Save at most this many lists and curations per creator
maxProductsPerCollectioninteger16Save up to 16 server-rendered products per idea list
requestRetriesinteger2Retry temporary or blocked responses with backoff
proxyConfigurationobjectdirect HTTPOptional Apify Proxy settings

Output examples

Creator profile

{
"handle": "sydneydelrey",
"name": "sydney del rey",
"description": "sharing all of my favorite Amazon finds ...",
"storefrontUrl": "https://www.amazon.com/shop/sydneydelrey",
"marketplace": "www.amazon.com",
"collectionCount": 21,
"scrapedAt": "2026-07-14T00:00:00.000Z"
}

Collection

{
"handle": "sydneydelrey",
"collectionType": "idea_list",
"collectionId": "KUGNMP73CKST",
"title": "vacay fitspo (from videos)",
"itemCount": 254,
"collectionUrl": "https://www.amazon.com/shop/sydneydelrey/list/KUGNMP73CKST"
}

Product

{
"handle": "sydneydelrey",
"collectionId": "KUGNMP73CKST",
"asin": "B0GS5LX63J",
"brand": "Muineobuka",
"title": "Backless Halter Tops for Women ...",
"productUrl": "https://www.amazon.com/dp/B0GS5LX63J"
}

Examples show the output shape, not a promise that any creator or item remains unchanged.

How much does it cost to scrape Amazon influencer storefronts?

The Actor uses pay-per-event pricing. A $0.005 Start charge covers run initialization, then an Item charge applies to every profile, collection, or product record saved.

Apify tierPrice per record
Free$0.000079721
Bronze$0.000069323
Silver$0.000054072
Gold$0.000041594
Platinum$0.000027729
Diamond$0.00001941

At the Bronze rate, 1,000 profile, collection, or product records cost about $0.0693, plus the Start charge. You can control cost with maxCollectionsPerStorefront, maxProductsPerCollection, and scrapeProducts. No Amazon account or paid third-party API key is required.

Monitoring creator-to-ASIN changes

Run the same input on a schedule and compare asin plus collectionId between snapshots. Useful alerts include:

  • 🆕 A creator adds a target brand or ASIN
  • 🗑️ A previously visible ASIN disappears
  • 📈 An idea list's advertised item count changes
  • 🏷️ A creator launches a new category-themed list
  • 🔗 A creator adds or changes a public social profile

Store snapshots in a named dataset, database, spreadsheet, or data warehouse outside this Actor when long-term history is required.

Integrations

Google Sheets

Schedule the Actor, export the Products dataset, and append new creator-to-ASIN rows for campaign research.

Slack or email alerts

Use an Apify webhook after each run, compare against the previous snapshot, and notify a partnership channel when target products appear.

CRM enrichment

Join creator handles and public social links to CRM records before partnership outreach.

Data warehouse

Load profiles, collections, and products as separate tables keyed by handle, collectionId, and asin.

Zapier and Make

Trigger the Actor from a no-code workflow and route completed dataset exports to Sheets, Airtable, or messaging tools.

API usage: run with the Apify API

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/amazon-influencer-storefront-scraper').call({
startUrls: [{ url: 'https://www.amazon.com/shop/sydneydelrey' }],
scrapeProducts: true,
maxCollectionsPerStorefront: 3,
maxProductsPerCollection: 8,
});
console.log(run.id);

Python

from apify_client import ApifyClient
import os
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/amazon-influencer-storefront-scraper').call(run_input={
'startUrls': [{'url': 'https://www.amazon.com/shop/sydneydelrey'}],
'scrapeProducts': True,
'maxCollectionsPerStorefront': 3,
'maxProductsPerCollection': 8,
})
print(run['id'])

cURL

curl -X POST \
"https://api.apify.com/v2/acts/automation-lab~amazon-influencer-storefront-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"startUrls":[{"url":"https://www.amazon.com/shop/sydneydelrey"}],"maxCollectionsPerStorefront":3,"maxProductsPerCollection":8}'

Use with Apify MCP

Connect AI clients through Apify MCP.

Claude Code

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=automation-lab/amazon-influencer-storefront-scraper"

Claude Desktop and Cursor

Add the server to Claude Desktop's or Cursor's MCP configuration:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com/?tools=automation-lab/amazon-influencer-storefront-scraper"
}
}
}

VS Code

Use the same Apify MCP URL in VS Code's MCP server settings and authenticate with your Apify account.

Example prompts:

  • “Extract the profile and first three lists from this Amazon influencer storefront.”
  • “Return the visible ASINs from this creator's idea-list URL.”
  • “Compare these creator storefronts and group recommended products by brand.”

Tips for reliable runs

  • Start with one creator and low limits.
  • Use a direct idea-list URL when only one list matters.
  • Keep retries enabled for temporary Amazon response variation.
  • Add an Apify Proxy configuration if direct access is limited for a marketplace.
  • Avoid unnecessary high concurrency; public storefront pages are the source of truth.
  • Treat price as optional and use the product URL for current product details.
  • Inspect logs if a creator renamed or removed a public storefront.

Supported URLs and marketplaces

The Actor accepts public URLs matching /shop/{handle} on common Amazon marketplaces, including the US, Canada, Mexico, Brazil, UK, Germany, France, Italy, Spain, Netherlands, Sweden, Poland, Belgium, Japan, India, Australia, Singapore, Turkey, UAE, and Saudi Arabia.

The marketplace is inferred from each URL. Markup and field availability can vary by domain and geography. A successful US test does not guarantee that every creator has an equivalent storefront on every marketplace.

Limitations

  • Amazon currently server-renders up to 16 visible product cards on an idea-list page; v1 intentionally caps extraction at that amount.
  • Curations are saved as collection metadata; products inside video/photo curation feeds are not expanded in v1.
  • Prices, discounts, delivery text, badges, and availability vary by session and region.
  • Private dashboards, commission data, buyer data, and Associates account data are not accessed.
  • Removed, renamed, geo-limited, or challenged storefronts can fail explicitly.
  • Amazon can change public markup, so stable IDs and URL fallbacks are used but future maintenance may be needed.

This Actor extracts information visible on public storefront pages. Public availability does not remove every legal or contractual obligation. You are responsible for your use case, local law, Amazon's applicable terms, intellectual-property rights, and personal-data requirements.

Use the data for legitimate research, analysis, interoperability, or monitoring. Do not use the Actor to access private accounts, circumvent authentication, impersonate people, harass creators, or send unlawful unsolicited messages. Store only the data you need and honor valid deletion or restriction obligations.

Troubleshooting

The run says the storefront was not accessible

Verify that the URL opens publicly and follows /shop/{handle}. The creator may have renamed, removed, or geo-limited the page. Retry later or configure Apify Proxy for the target marketplace.

I received a profile but no products

Confirm scrapeProducts is true and that selected collections include idea lists. Curations can contain posts rather than server-rendered product cards. Try a direct idea-list URL if you know the target list.

Some products have no price

Amazon does not display a numeric price on every public card. The Actor keeps priceText nullable and can return availabilityText instead. Use productUrl or a dedicated product scraper for current product detail enrichment.

Where are collections and products?

Open the run's Storage tab and select the collections or products dataset. The default dataset contains creator profiles.

Use this Actor when the key relationship is creator → collection → product. Use a product, review, or seller Actor when deeper marketplace entity data is the primary goal.

FAQ: frequently asked questions

Does this require an Amazon login?

No. The Actor is designed for anonymous public storefront and idea-list pages.

Can I scrape multiple creators in one run?

Yes. Add multiple storefront URLs to startUrls and keep bounded limits for predictable duration.

Can I target one idea list?

Yes. Submit its full /shop/{handle}/list/{id} URL.

Does it find influencer storefronts by keyword?

No. V1 extracts known public storefront URLs; it does not claim to provide Amazon-wide creator discovery.

Are results real-time?

Each run reads the public pages available at run time and adds scrapedAt timestamps.

Can I use the data in an AI workflow?

Yes. Typed schemas, separate datasets, API access, and Apify MCP make the output suitable for agent and data workflows.

Data quality notes

Identifiers come from Amazon's public URLs and content attributes. Products are deduplicated by ASIN within each requested collection. Collections are deduplicated by type and Amazon collection ID. Repeated duplicate input URLs are processed once per run.

The Actor fails when it cannot identify a public storefront rather than silently returning an empty successful run. That behavior helps scheduled monitors distinguish “no change” from “source unavailable.”