Amazon Store Profile

Affiliate disclosure: TrueFetch may earn a commission when you open an Apify account through links on this page, at no extra cost to you.

Amazon Store Profile turns one supported Amazon Brand Store page URL into a structured Store and observed-product profile for developers, data teams, and brand researchers.

• Strict URL contract: accepts one Amazon Brand Store /stores/.../page/{id} URL from a supported marketplace.
• Twenty documented fields: returns store identity, market, page metadata, visuals, categories, products, and processing context when available.
• One-result delivery: writes one successful Store profile to the default Apify Dataset for export or automation.
• Transparent billing: charges the start, variable Actor usage, and one Store result; products are not a separate charged event.

Run a one-result test · View API

The smallest useful test is one valid Store URL and one successful result: at an illustrative 200 usage events, the free-tier event total is $0.21200; usage varies, so set a maximum total charge where available.

What does Amazon Store Profile do?

Amazon describes a Brand Store as a dedicated destination where an eligible brand can present products, story, imagery, and collections. Its URL provides evidence of how a brand presents itself in one Amazon marketplace.

Amazon Store Profile converts that public page into one consistent record. It can return the store or brand name, country, storefront title, description, page configuration values, brand color and theme, hero and logo URLs, category navigation, featured links, observed product records, product counts, page title, and deduplicated media. Processing fields identify the Actor and retrieval time.

Output is conditional because Amazon does not expose every module on every Store. Recommendation or promotional links can enter the observed product collection, so check brand relevance. Empty optional values are omitted. A Dataset row is a snapshot, not a complete Amazon catalog.

The result does not establish brand ownership, seller authorization, inventory, sales, advertising performance, or legal compliance. Those conclusions need independent evidence.

How do I run Amazon Store Profile?

1. Open the Actor in Apify Console.
2. Paste one supported Brand Store page URL into store_url; use this Anker Store path for an initial test:

{
  "store_url": "https://www.amazon.com/stores/Anker/page/A48F6E37-FE73-4607-A1E9-B2E0AE587FCB"
}

3. Start the run. One run accepts one Store URL and can write at most one Store result.
4. Open the default Dataset. Confirm one item exists, processor and processed_at are current, and country matches the submitted marketplace. Optional example fields may be absent.

If the Dataset is empty, confirm the URL still resolves to a public Brand Store with /stores/, optional brand slug, /page/, and an identifier. Product, seller, search, and short brand routes are invalid.

What data does Amazon Store Profile return?

A successful record can contain twenty top-level fields. Only processor and processed_at are constructed unconditionally; other fields appear when the Store response provides meaningful values.

Field	Meaning
processor, processed_at	Actor URL and ISO retrieval timestamp
name, storefront_name, description	Store identity and descriptive text
country, country_code	Marketplace location and short code
page_version, last_submitted_at	Store configuration version and submission time when exposed
brand_color, theme	Store design values when exposed
hero_url, logo_url	Primary brand imagery
categories	Navigation records with name, URL, hierarchy, parent, and optional product count
featured_products	Product links featured outside the main returned product collection
products	Deduplicated product links and records observed across fetched Store pages, including ProductGrid data when available
product_count	Count of records in products
page_title	HTML title associated with the Store page
images, videos	Deduplicated media URLs found across fetched Store pages

Product objects can include ASIN, URL, title, brand, media, price, rating, review count, availability, badges, taxonomy, variations, and Store category context.

{
  "processor": "https://apify.com/truefetch/amazon-store-profile?fpr=aiagentapi",
  "processed_at": "2026-07-24T16:00:00+00:00",
  "name": "Amazon.com : Anker",
  "country": "United States",
  "country_code": "US",
  "storefront_name": "Amazon.com : Anker",
  "description": "Amazon.com : Anker",
  "hero_url": "https://m.media-amazon.com/images/S/example-hero.jpg",
  "featured_products": [
    {"asin": "B09C5RG6KV", "url": "https://www.amazon.com/dp/B09C5RG6KV"}
  ],
  "products": [
    {"asin": "B09C5RG6KV", "url": "https://www.amazon.com/dp/B09C5RG6KV", "store_categories": ["Home"]}
  ],
  "product_count": 20,
  "page_title": "Amazon.com : Anker",
  "images": ["https://m.media-amazon.com/images/S/example-store.jpg"],
  "videos": ["https://m.media-amazon.com/images/S/example-store-video.mp4"]
}

This is a compact illustration based on the shared test scenario, not a guarantee that those assets remain live. The Dataset from your run is authoritative.

What inputs can I configure?

The schema exposes one required string:

Field	Type	Required	Accepted format
store_url	string	Yes	Full supported Amazon Brand Store URL matching /stores/{optional-brand}/page/{id}

The URL must use HTTP or HTTPS. The hostname must exactly match a supported Amazon marketplace, and the path must contain a Brand Store page identifier. An unrelated hostname containing “Amazon,” an unsupported regional domain, or a path without the Brand Store pattern is rejected.

Each run accepts one Store. Applications monitoring a list should start separate runs, retain the association between input and run ID, set explicit charge and timeout controls where available, and distinguish an empty Dataset from a failed run.

What platforms and markets does Amazon Store Profile cover?

Supported hosts currently include Amazon United States, Canada, United Kingdom, Germany, France, Italy, Spain, Japan, Australia, and India: amazon.com, amazon.ca, amazon.co.uk, amazon.de, amazon.fr, amazon.it, amazon.es, amazon.co.jp, amazon.com.au, and amazon.in, including their www forms.

Coverage means the input validator recognizes those hosts; it does not mean every brand has a Store in every market. Store IDs, page modules, language, assortment, availability, pricing, and media can differ across country sites. Compare like-for-like URLs and retain country, country_code, and processed_at when building a cross-market dataset.

The Actor targets Brand Store pages, not ordinary Amazon product pages, search results, seller profiles, affiliate influencer storefronts, or private Seller Central information.

Why use Amazon Store Profile?

Manual Store review is difficult to repeat across brands, markets, and dates. Structured records support comparison, scheduling, export, and validation while keeping Store context beside observed products.

Capability	Practical benefit
One strict Brand Store URL input	Keeps each run attributable to one Store and marketplace
Twenty documented top-level fields	Gives data teams a stable Store-level record while preserving source-dependent omissions
Store navigation plus observed product records	Keeps page and category context beside the product links observed on the page
Dataset, API, scheduling, webhooks, and MCP access	Reuses the same one-field contract from a browser, pipeline, or connected AI client

The main trade-off is scope: the Actor returns a current Store-page snapshot, not a complete catalog, seller account, inventory feed, or historical offer database. You remain responsible for checking source suitability and interpreting missing fields.

Who is Amazon Store Profile for?

Developers and data teams can add a timestamped Store snapshot to internal brand records, scheduled monitoring, or review queues. Brand and ecommerce analysts can monitor Store identity, visual assets, navigation, and returned product counts. Competitive-research teams can compare Store architecture within the same market. Catalog teams can collect public Store-page product observations before reconciling them with a separate product source. Agencies can review campaign landing destinations and creative consistency.

It can also support human-led lead qualification by showing whether a company maintains a curated Amazon presence. A Store page alone does not prove revenue, operational scale, seller authorization, or willingness to engage, so high-impact conclusions should not be automated from this record alone.

How can I use Amazon Store Profile through the API or MCP?

The Actor ID is truefetch/amazon-store-profile. Start an asynchronous run through the REST API, then read the default Dataset after the run reaches SUCCEEDED:

$curl -X POST "https://api.apify.com/v2/acts/truefetch~amazon-store-profile/runs?token=$APIFY_TOKEN&waitForFinish=180" -H "Content-Type: application/json" -d '{"store_url":"https://www.amazon.com/stores/Anker/page/A48F6E37-FE73-4607-A1E9-B2E0AE587FCB"}'

Check terminal status and Dataset count separately. Keep the API token secret and out of repositories, datasets, and support messages.

Apify's current hosted MCP endpoint uses Streamable HTTP. Configure an MCP-compatible client with OAuth, or add an authorization header with an Apify token kept outside source control:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN>"
      }
    }
  }
}

After connecting, discover truefetch/amazon-store-profile and run it with the same input:

{
  "store_url": "https://www.amazon.com/stores/Anker/page/A48F6E37-FE73-4607-A1E9-B2E0AE587FCB"
}

MCP execution depends on account, token permissions, and Actor visibility. Discover the latest schema first; see Apify's MCP documentation.

How much does Amazon Store Profile cost?

Amazon Store Profile uses pay-per-event pricing. Review the live pricing panel before each production rollout because rates and platform behavior can change.

Billed event	Free	Bronze	Silver	Gold	Platinum	Diamond
Actor usage	$0.00001	$0.00001	$0.00001	$0.00001	$0.00001	$0.00001
Actor start	$0.01000	$0.01000	$0.01000	$0.01000	$0.01000	$0.01000
Successful Store result	$0.20000	$0.19333	$0.18667	$0.18000	$0.18000	$0.18000

For an illustrative successful run with one result and 200 usage events, the estimate is (200 × $0.00001) + $0.01000 + $0.20000 = $0.21200. Paid plan tiers may reduce the Result event price.

Embedded products are not separately charged. A failed or zero-row run may still incur Start and Usage; validate the URL and set a charge cap where supported.

How does Amazon Store Profile compare with alternatives?

Manual browsing preserves page context but is slow to repeat and difficult to export. A general browser scraper may capture raw HTML or text, but downstream code must still recognize Store modules and normalize products. Amazon's seller tools serve eligible brand owners and operational workflows; they are not a drop-in source for public cross-brand research. Commercial marketplace datasets may offer broader historical coverage but often use different definitions and update schedules.

This Actor is focused: one supported Brand Store URL produces one normalized page snapshot. Choose it when that contract fits. Combine it with a dedicated product or price source when you need broader catalog coverage, offer history, seller details, or inventory signals.

What are the limits and troubleshooting steps?

Amazon can change page structure, regional access, modules, media URLs, product availability, recommendations, and promotional placements. Some fields may be absent, Store assets may expire, and observed prices or ratings may vary with time and shopper context. products represents deduplicated product links and records observed across the fetched Store pages, including ProductGrid data when available. It can include recommendation or promotional items that are not owned by the Store brand, so validate ASIN and brand relevance before enrichment or catalog joins.

For a rejected input, verify the exact hostname and /stores/.../page/{id} path. For an empty Dataset, open the page and confirm that it remains public, then inspect run status and logs. For partial output, compare the Store modules visible in the same marketplace and time window. For an API or MCP issue, confirm token permissions, Actor visibility, the latest schema, timeout, and charge cap. Preserve a sanitized URL and run ID when requesting help.

Frequently asked questions

Does this accept Amazon product or seller URLs? No. It requires a supported Brand Store page path.

Can one run process multiple Stores? No. Start one run per store_url.

Are all twenty fields always present? No. Optional empty values are omitted because Store modules vary.

Does products contain the full brand catalog? No. It contains deduplicated product records observed on fetched Store pages.

Can products include an item from another brand? Yes. Amazon can render recommendations or promotional product links around Store content. Treat the collection as observed page evidence and validate brand, ASIN, and category relevance before joining it to a catalog.

Can I monitor changes? Yes. Schedule repeated runs and compare equivalent URLs, marketplaces, and fields while retaining timestamps.

Are prices, ratings, and media current forever? No. They reflect the retrieval snapshot and may change or expire.

Related TrueFetch Actors

Use Amazon Price Tracker for price-focused monitoring, Google Maps Business Listing for local business details, or LinkedIn Company Profile for professional company enrichment. Each Actor has its own input, output, price, coverage, and legal context.

Support and last updated

Use the Issues tab or TrueFetch support. Include a sanitized URL, run ID, expected and actual behavior, and a short log excerpt; remove tokens and private data.

Amazon Store Profile is independent and not endorsed by Amazon. Comply with current terms, Apify policies, law, privacy, and intellectual-property obligations.

Amazon's official Brand Stores page describes the dedicated Store experience and how shoppers can reach it, while the seller FAQ explains Store eligibility. These sources describe Amazon's product; they do not endorse this Actor.

Use the Store page, API page, or Issues. For community help, contact the TrueFetch group; for direct support, contact TrueFetch support.

Last updated: July 24, 2026. The live schema, pricing panel, Dataset, and Amazon documentation are authoritative.

Run one current Store profile · Review the API options