Amazon Price Tracker

Affiliate disclosure: Apify links on this page may include referral parameters. If you sign up through them, TrueFetch may receive a commission at no extra cost to you.

Amazon Price Tracker is an Amazon product search and price monitoring API that collects current, source-linked listings from 22 country storefronts in one normalized dataset for developers, retail analysts, and data teams.

• 22 selectable Amazon storefronts cover North America, Europe, Asia-Pacific, the Middle East, and Brazil.
• 58 normalized dataset fields preserve product identity, price, offers, availability, ratings, sellers, source links, and processing context.
• 3 required inputs make each search explicit: keyword, country storefront, and per-run result ceiling.
• Current Store evidence: 7 total users, 1 monthly active user, and one 5.0 rating were visible on 2026-07-21; these are historical publishing signals, not performance guarantees.

Run the minimum 10-result test · View API

The smallest valid max_results value is 10. If 10 records are stored, the FREE-tier Actor event charge is at most $0.10300: one $0.01000 start plus 10 results at $0.00930 each, excluding separate Apify platform usage.

What does Amazon Price Tracker do?

Amazon Price Tracker searches the public product results for one chosen Amazon country storefront. A run accepts a product name, model, brand, or category query, then returns publishable listings in a consistent 58-field Dataset. The normalized record keeps numeric prices beside original price text, preserves product and source URLs, and adds the marketplace country and search rank so downstream comparisons remain traceable.

This Actor returns a current public search snapshot. It does not maintain a built-in price history, calculate price changes, send alerts, edit seller listings, place orders, or represent an official Amazon API. It also does not guarantee that every optional field will be present. Amazon storefronts can expose different identifiers, offer details, delivery messages, and availability signals for different products and locations.

How do I run Amazon Price Tracker?

1. Open Amazon Price Tracker in Apify Store.
2. Enter a specific product query, such as a model name rather than a broad category.
3. Choose one of the 22 supported Amazon country storefronts.
4. Set max_results from 10 to 10,000, start the run, and review the default Dataset.

Use this minimum valid input for a small US storefront check:

{
  "keyword": "Sony WH-1000XM5",
  "country": "United States",
  "max_results": 10
}

For this single-store Actor, max_results is the maximum number of product records stored for the run. It is a ceiling rather than a promise: fewer records can be returned when the public search surface exposes fewer publishable listings.

What data does Amazon Price Tracker return?

Every stored item uses the same 58-field contract. Optional values remain empty when the storefront does not expose reliable data for that listing.

Data group	Dataset fields
Images and content	main_image, image_urls, title, brand, badges, category, breadcrumbs, description, features
Product identity	product_id, sku, gtin, mpn, model, specifications, manufacturer, origin, energy_class, included, condition, release_date, variant_group, variants
Price and promotion	price, was_price, unit_price, currency, price_text, discount_pct, discount_text, promo_text, installment_text
Availability and demand	stock_status, stock_text, sales_text, buy_limit
Rating and seller	rating, review_count, seller, seller_url, seller_score
Fulfillment	shipping_text, shipping_cost, delivery_text, pickup_text, return_text, return_days, warranty_text
Search context	platform, site, country, product_url, source_url, query, rank, sponsored
Processing context	processor, processed_at

This abbreviated illustrative item follows the Sony headphone scenario:

{
  "title": "Sony WH-1000XM5 Wireless Headphones",
  "brand": "Sony",
  "price": 349.99,
  "currency": "USD",
  "stock_status": "in_stock",
  "rating": 4.6,
  "review_count": 8421,
  "platform": "amazon",
  "site": "amazon.com",
  "country": "US",
  "product_url": "https://www.amazon.com/dp/EXAMPLE",
  "source_url": "https://www.amazon.com/s?k=Sony+WH-1000XM5",
  "query": "Sony WH-1000XM5",
  "rank": 1,
  "processor": "https://apify.com/truefetch/amazon-price-tracker",
  "processed_at": "2026-07-21T12:00:00"
}

Use product_url to revisit the listing and source_url to preserve the search context. Confirm the current contract on the live Output schema before enforcing strict downstream validation.

What inputs can I configure?

Input	Type	Required	Accepted behavior	Example
keyword	string	Yes	A non-empty product, brand, model, or search phrase	Sony WH-1000XM5
country	string	Yes	One exact country name from the 22-value schema enum	United States
max_results	integer	Yes	A result ceiling from 10 through 10,000	10

All three inputs are genuinely required. The Actor does not replace missing values with hidden defaults, and an unsupported country is not silently redirected to another storefront. Use a narrower keyword when the goal is model-level price research; broad category queries can return heterogeneous products that are not direct substitutes.

What platforms and markets does Amazon Price Tracker cover?

This Actor targets Amazon only, but it can route a query to 22 supported country storefronts:

Region	Supported country storefronts
North and South America	Brazil, Canada, Mexico, United States
Europe	Belgium, France, Germany, Ireland, Italy, Netherlands, Poland, Spain, Sweden, Turkey, United Kingdom
Asia-Pacific	Australia, India, Japan, Singapore
Middle East and North Africa	Egypt, Saudi Arabia, United Arab Emirates

Country selection controls the Amazon site used for the search. Coverage does not imply that the same catalog, currency, seller offers, shipping eligibility, language, or stock state appears in every storefront. Amazon's official Business marketplace documentation also treats marketplaces as country-specific URLs; the Actor's current input schema and verified local routing remain the authority for the exact 22 supported values in this release.

Why use Amazon Price Tracker?

Verified capability	Practical benefit
One schema across 22 Amazon sites	Compare storefront snapshots without rebuilding columns for each country.
Numeric and source-form price values	Analyze price while retaining price_text for verification.
Product URL plus search source URL	Trace both the listing and the query context that produced it.
Nullable offer, seller, and fulfillment fields	Preserve honest source gaps instead of filling them with guessed values.
Rank and sponsored indicators	Separate search-position context from product identity when the source exposes it.

The main trade-off is source dependence. Normalization makes records easier to compare, but it cannot make two Amazon storefronts carry the same offer or expose identical fields. For longitudinal monitoring, schedule repeated runs and store the resulting Datasets in your own history layer.

Who is Amazon Price Tracker for?

Amazon Price Tracker is designed for developers, retail intelligence teams, ecommerce analysts, and data practitioners who need repeatable public search snapshots. Typical uses include model-level price checks across storefronts, assortment reviews, promotion research, seller and availability monitoring, catalog enrichment, and input feeds for internal shopping research tools.

It is not the right choice for sellers who need to create or update Amazon listings, access account-specific inventory, or use contracted catalog data. Amazon's official Selling Partner APIs serve authorized seller workflows and require the relevant account authorization and roles. This Actor is also a poor fit when exact cross-country product matching, automatic alerts, or guaranteed real-time inventory is mandatory; those require additional services beyond the returned search records.

How can I use Amazon Price Tracker through the API or MCP?

The public Actor identifier is truefetch/amazon-price-tracker, and the current platform ID is pQOQjtgMgSPerjTkh. The live API page provides generated HTTP, SDK, CLI, OpenAPI, and MCP references.

Use the synchronous Dataset endpoint for the shared Sony scenario:

curl -X POST "https://api.apify.com/v2/acts/truefetch~amazon-price-tracker/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "Sony WH-1000XM5",
    "country": "United States",
    "max_results": 10
  }'

Apify currently recommends its hosted MCP server over the deprecated SSE transport. A client that supports tool filtering can expose only this Actor:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=truefetch/amazon-price-tracker"
    }
  }
}

After OAuth authorization, ask the client to run truefetch/amazon-price-tracker with the same three-field input. Running Actors and reading run storage requires authentication; follow the current Apify MCP server documentation for client-specific setup.

How much does Amazon Price Tracker cost?

Amazon Price Tracker uses pay-per-event billing: one start event per run and one result event for every record stored in the default Dataset.

Apify tier	Actor start	Price per stored result
FREE	$0.01000	$0.00930
BRONZE	$0.01000	$0.00899
SILVER	$0.01000	$0.00868
GOLD	$0.01000	$0.00837
PLATINUM	$0.01000	$0.00837
DIAMOND	$0.01000	$0.00837

At the smallest accepted limit, a FREE-tier run storing 10 results has an Actor event charge of $0.01000 + (10 × $0.00930) = $0.10300. Fewer stored records produce fewer result events. Separate Apify platform usage may apply, and prices can change, so verify the live pricing page before budgeting a large run.

How does Amazon Price Tracker compare with alternatives?

Option	Best fit	Important trade-off
Amazon Price Tracker	Public keyword searches across 22 Amazon storefronts with one normalized Dataset	Snapshot only; optional fields and result counts depend on the storefront
Product Price Tracker	Comparing Amazon with other supported marketplaces in one run	Broader scope can produce more records and a less Amazon-specific workflow
Amazon Selling Partner APIs	Authorized catalog, listing, and seller operations	Requires suitable seller authorization and roles; serves a different workflow
Manual Amazon searches	A few one-off visual checks	Difficult to repeat, export, and compare consistently across dates or countries

Choose this Actor when the decision starts with a public search query and needs source-linked records. Choose an official Amazon integration when the decision depends on authenticated seller data or listing operations. Choose the broader Product Price Tracker when cross-marketplace comparison matters more than Amazon-only focus.

What are the limits and troubleshooting steps?

Symptom or limit	Explanation and next step
No records are stored	Confirm the exact country name, use a recognizable product query, and retry with max_results: 10.
Fewer than 10 results appear	The limit is a ceiling; the storefront may expose fewer publishable listings for that query.
Price or seller fields are empty	Open product_url or source_url; the public result may not expose that value.
Results differ between countries	Each country selection uses a different storefront, catalog, currency, and offer context.
Similar products appear multiple times	Search listings are not guaranteed to be globally deduplicated or matched by model.
A scheduled snapshot changes	Public rankings, offers, availability, and sponsored placement can change between runs.
Cost is higher than expected	Count stored Dataset items and compare that count with the per-result event price.

For a reproducible issue, submit the run ID, one keyword, one exact country, max_results: 10, and the expected versus observed outcome. Do not include your Apify token or account credentials in an issue.

Frequently asked questions

Does Amazon Price Tracker keep a price history?

No. Each run creates a current public search snapshot. Schedule repeated runs and retain their Datasets when you need a time series.

Can I search more than one Amazon country in a run?

No. country is one required string. Run the Actor separately for each storefront you want to compare.

Why can two storefronts return different products for the same keyword?

Amazon catalogs, sellers, rankings, languages, currencies, and availability differ by country. The Actor preserves that storefront-specific context rather than forcing artificial equality.

Are price and price_text redundant?

No. price is suitable for numeric analysis, while price_text retains the source-facing representation for verification.

Does the Actor require Amazon seller credentials?

No Amazon credential is a public input. An Apify account and token are required only for authenticated API or MCP execution.

Does it update or manage Amazon listings?

No. The Actor collects public search records. Use the appropriately authorized Amazon Selling Partner API for seller listing operations.

Can I schedule recurring Amazon price checks?

Yes. Apify scheduling can rerun the Actor. The Actor itself does not calculate deltas or send price-change alerts.

How is billing counted when a product has many optional fields?

Billing is per stored result record, not per populated field. One stored product item triggers one result event.

Related TrueFetch Actors

• Product Price Tracker searches Amazon together with compatible marketplaces when cross-store comparison is the goal.
• eBay Price Tracker focuses on active marketplace listings, conditions, shipping, and seller context.
• Walmart Price Tracker focuses on Walmart retail and marketplace search records.

Support and last updated

Use the Store page, API page, and Issues tab for Actor-specific work. Community help is available in the TrueFetch group, and direct support is available through AiAgentApi.

Last verified: 2026-07-21. Local schemas and read-only runtime evidence control capability claims; Store statistics and indexed snippets are treated as dated publishing evidence when they lag behind the current project.

Start the minimum valid Amazon check · Open the generated API reference