Myntra Price Tracker
Pricing
from $7.47 / 1,000 results
Myntra Price Tracker
A myntra price tracker api that searches India fashion listings and returns 55-field INR price, discount, brand, availability, rating, image, rank, and source records through three inputs.
Pricing
from $7.47 / 1,000 results
Rating
0.0
(0)
Developer
TrueFetch
Maintained by CommunityActor stats
2
Bookmarked
3
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Myntra Price Tracker is a myntra price tracker api that searches Myntra by keyword and returns 55 normalized product, offer, seller, availability, rank, and source fields for fashion-data developers and merchandising teams researching current India offers.
- Four public inputs, three required:
keyword,country, andmax_resultsare required;platformsis optional. - 1 supported market and 1 selectable platform value are stated directly in the input schema.
- 55 public Dataset fields keep product identity, price, seller, fulfillment, reputation, and provenance in one row shape.
- Pay-per-event pricing charges $0.01000 per Actor Start and one tiered Result event for each stored Dataset row.
Run a one-result test · View API
Set max_results to 1 and select one platform. At the FREE rate, one stored row costs at most $0.01830 including Actor Start; an empty Dataset adds no Result event.
What does Myntra Price Tracker do?
Myntra Price Tracker turns a current keyword search into source-linked product rows that can be exported or consumed through the Apify API. The tested scenario uses running shoes in India and requests up to 7 results from Myntra. Each accepted row can include identifiers, current and previous price text, discounts, availability, seller context, ratings, fulfillment text, rank, and the originating URL.
Myntra offers catalog shows that fashion search exposes changing prices, discounts, brands, sizes, ratings, and sorting choices. This independent Actor records source-visible observations; it does not create history, guarantee local stock, place orders, or infer missing values.
How do I run Myntra Price Tracker?
Run Myntra Price Tracker by supplying the keyword, an allowed country, a positive result limit, and optionally the platform selection.
- Open the Input page and keep the prefilled tested example or replace
keywordwith the product phrase you need. - Choose one of the 1 allowed
countryvalues. Keepplatformsempty to use all eligible routes, or select only values allowed by this edition. - Set
max_resultsto a positive integer. The limit applies per selected platform; there is no artificial 10,000-result schema ceiling. - Start the run, then open the default Dataset to inspect, filter, or export the rows.
{"keyword": "running shoes","country": "India","max_results": 7,"platforms": ["Myntra"]}
This tested profile returned 7 Dataset rows. Live marketplaces may return fewer for narrow queries, removed products, or unavailable routes.
What data does Myntra Price Tracker return?
Myntra Price Tracker returns one normalized product observation per Dataset row, with 55 documented public fields grouped below.
| Group | Public fields |
|---|---|
| Media | image_url, image_urls |
| Identity and catalog | title, brand, badges, category, breadcrumbs, description, features, product_id, sku, gtin, mpn, model, specifications, manufacturer, origin, energy_class, included, condition, release_date, variants |
| Price and promotion | price, was_price, unit_price, currency, price_text, discount_pct, discount_text, promo_text, installment_text |
| Availability and fulfillment | stock_status, stock_text, sales_text, shipping_text, shipping_cost, delivery_text, pickup_text, return_text, return_days, warranty_text |
| Reputation and seller | rating, review_count, seller, seller_url, seller_score |
| Provenance | platform, site, country, product_url, source_url, rank, is_sponsored, processor, processed_at |
This is an abbreviated, illustrative 13-field item from the shared scenario; the effective Dataset schema contains 55 fields, and arrays or unavailable values may be empty:
{"title": "Skechers Men Running Shoes Go Run 7.0 Running Shoes","brand": "Skechers","price": 5399.0,"currency": "INR","stock_status": "in_stock","rating": 4.285714149475098,"review_count": 14,"seller": "","platform": "myntra","country": "IN","rank": 1,"is_sponsored": true,"processed_at": "2026-08-11T03:29:46+00:00"}
Use product_id, sku, gtin, mpn, model, and product_url for identity checks before deduplicating. rank is the collected search position, is_sponsored reflects the source signal when present, and processed_at records processing time. Export the Dataset as JSON, CSV, Excel, XML, RSS, or another format supported by Apify.
What inputs can I configure?
Myntra Price Tracker exposes exactly four public inputs in schema order, including three required fields and one optional array.
| Parameter | Type | Required | Description | Tested example |
|---|---|---|---|---|
keyword | string | Yes | Product phrase, brand, or model to search on Myntra. | "running shoes" |
country | string | Yes | Storefront country for Myntra; this edition supports 1 market. | "India" |
max_results | integer | Yes | Maximum product records returned per selected platform; enter any integer greater than zero. | 7 |
platforms | array | No | Optional platform selection fixed to Myntra; choose it or leave the list empty. | ["Myntra"] |
platforms remains a real input in fixed editions: choose the edition's singleton value or leave the array empty, which preserves the fixed route. The Actor respects the supplied keyword, country, and positive max_results; it does not silently replace them with unrelated defaults.
What platforms and markets does Myntra Price Tracker cover?
Myntra Price Tracker covers only the platform and market combinations represented by its effective enums and runtime route map.
The effective schema contains 1 country value: India. The platforms input contains 1 value: Myntra.
Country selection changes the storefront or regional route where the platform supports it. It does not promise that every product, seller, delivery option, or language is available in every market. When a source shows localized currency, title, shipping, or promotion text, the row preserves that source-facing context.
Why use Myntra Price Tracker?
Use Myntra Price Tracker when a current, normalized Dataset is more useful than repeatedly copying search cards by hand.
| Capability | Practical benefit |
|---|---|
| Keyword-driven search | Reuse a product phrase across scheduled or API-triggered runs. |
| 55-field row contract | Keep downstream columns stable while source coverage varies. |
| Country and platform enums | Reject unsupported market combinations before a run starts. |
| Source URLs and processing time | Trace an observation back to the marketplace and its collection time. |
| Pay per stored result | Estimate row cost before running a bounded test. |
The main trade-off is explicit: fashion variants and sizes are source-dependent, and a search row is not an inventory guarantee. Treat rows as current observations, validate important purchasing decisions against the linked source, and design monitoring jobs to store snapshots in your own system.
Who is Myntra Price Tracker for?
Myntra Price Tracker is for fashion-data developers and merchandising teams researching current India offers who need to compare running-shoe prices, brands, discounts, and ratings.
- Fashion Price Checks. Use
title,price,currency,seller,stock_status, andsource_urlto support fashion price checks. - Brand Assortment Research. Use
title,price,currency,seller,stock_status, andsource_urlto support brand assortment research. - Discount Snapshots. Use
title,price,currency,seller,stock_status, andsource_urlto support discount snapshots. - Rating Comparison. Use
title,price,currency,seller,stock_status, andsource_urlto support rating comparison. - Product Discovery Feeds. Use
title,price,currency,seller,stock_status, andsource_urlto support product discovery feeds.
It is not the right choice for checkout automation, personal account actions, guaranteed store inventory, completed-sale appraisal, or a turnkey alert dashboard. Choose it when you own the downstream comparison, storage, alerting, or analysis workflow and want a bounded collection component.
How can I use Myntra Price Tracker through the API or MCP?
Use Actor ID yff3Hh7lpcCkZ92uT or name form truefetch/myntra-price-tracker through Apify API v2, an official API client, or the hosted Apify MCP server.
Actor ID
yff3Hh7lpcCkZ92uT
The stable name form is truefetch/myntra-price-tracker.
HTTP
curl -X POST 'https://api.apify.com/v2/acts/yff3Hh7lpcCkZ92uT/run-sync-get-dataset-items?token=$APIFY_TOKEN' \-H 'Content-Type: application/json' \-d '{"keyword": "running shoes", "country": "India", "max_results": 7, "platforms": ["Myntra"]}'
MCP
Apify's hosted MCP server uses Streamable HTTP. Configure it with a bearer token, then ask the call-actor tool to run the name form and pass the same input:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=actors","headers": {"Authorization": "Bearer <APIFY_TOKEN>"}}}}
Use Actor truefetch/myntra-price-tracker with this input:
{"keyword": "running shoes","country": "India","max_results": 7,"platforms": ["Myntra"]}
The live API page provides generated endpoints and SDK examples. The official Apify MCP documentation explains Streamable HTTP, OAuth, bearer-token authentication, tool selection, and how agents discover and call Actors.
How much does Myntra Price Tracker cost?
At the FREE tier, Myntra Price Tracker costs $0.00830 per stored Result row plus $0.01000 per Actor Start, so the smallest one-row test costs $0.01830.
| Event | Plan tier | Unit price | Billing unit |
|---|---|---|---|
| Actor Start | All | $0.01000 | Once when the run starts |
| Result | Free | $0.00830 | Each row stored in the default Dataset |
| Result | Bronze | $0.00747 | Each row stored in the default Dataset |
| Result | Silver | $0.00664 | Each row stored in the default Dataset |
| Result | Gold | $0.00623 | Each row stored in the default Dataset |
| Result | Platinum | $0.00623 | Each row stored in the default Dataset |
| Result | Diamond | $0.00623 | Each row stored in the default Dataset |
The Result event fires once for each row stored in the default Dataset. With max_results: 1 and one selected platform, the maximum first-test calculation is $0.01000 + 1 × $0.00830 = $0.01830. Empty runs still incur Actor Start but no Result row charge. Prices can change, so confirm the live Pricing page before a large run.
How does Myntra Price Tracker compare with alternatives?
Myntra Price Tracker is best when you need repeatable product rows and API delivery without maintaining a separate collection contract for this route.
- Manual browsing is appropriate for a one-off purchase decision, especially when you must confirm local stock or a final checkout total. It stops scaling once you need repeated, structured rows.
- Separate source integrations give maximum control when your team already owns credentials, schemas, retries, and storage for every marketplace. They increase maintenance when the workflow spans more than one route.
- The source's official site or offering is the right place to purchase, manage an account, confirm delivery, or use first-party customer features. This Actor observes public search data and never substitutes for those actions.
- A hosted price-history product is better when you need an existing historical chart or managed alerts. This Actor supplies current rows that your own scheduler and database can retain over time.
Choose something else if you need guaranteed item matching, checkout execution, private account data, or a source-supported inventory commitment.
What are the limits and troubleshooting steps?
The main limits of Myntra Price Tracker come from live search behavior, regional catalog differences, and the meaning of a keyword result.
- Dataset is empty → the keyword may be too narrow, the selected country/platform pair may have no products, or the source may be unavailable. Retry the smallest profile with a broader product phrase and
max_results: 1. - Fewer rows than
max_results→max_resultsis a ceiling, not a promise. The route stores only usable products it receives. - Several similar products → marketplaces can show variants, bundles, accessories, or multiple sellers. Match on identifiers and URLs instead of title alone.
- Price or stock differs later → rows are observations at processing time. Recheck
product_urland schedule a new run for a new snapshot. - Some fields are empty → the 55-field schema is cross-platform; not every source publishes every identifier, seller score, return term, or warranty value.
- Run takes longer than expected → source response and the number of selected routes affect duration. Reduce
max_results, select one platform, and review the run log.
For a reproducible problem, open an Issue with the run ID, exact input, expected behavior, and one affected source URL. Do not post API tokens, account data, or private customer information.
Frequently asked questions
Myntra Price Tracker answers the following common implementation and buying-decision questions directly.
How do I track myntra product prices by keyword?
Run truefetch/myntra-price-tracker with a precise keyword, an allowed country, a small positive max_results, and the relevant platforms value. Store successive Datasets in your own system if you need comparisons over time.
Can I use a myntra price monitoring api for india?
Yes. The Actor exposes one four-input contract and returns the same 55-field Dataset shape without requiring a separate marketplace credential from you; an Apify token is still required for authenticated API or MCP runs.
Is there a free product price API?
There is no permanently free promise. Apify accounts may include platform credits, but this Actor bills $0.01000 for Actor Start and $0.00830 per Result on the FREE subscription tier; check the live pricing page.
Can I schedule runs to monitor product prices over time?
Yes. Use Apify schedules with a bounded input, then persist each Dataset in your database or integration. The Actor returns snapshots and does not itself calculate price changes or send alerts.
Does max_results apply to the whole run?
No. It is a per-selected-platform ceiling. A multi-platform run can therefore store more than max_results rows, while a fixed edition with one route cannot exceed that ceiling.
Why are some of the 55 fields empty?
Because source cards and product pages do not expose identical attributes. Empty values distinguish unavailable source data from fabricated or guessed values.
Does the Actor guarantee the lowest price or local stock?
No. Search relevance, seller offers, delivery location, promotions, and inventory can change. Use the row's source link for a final purchasing or operational decision.
Related TrueFetch Actors
These three TrueFetch Actors are the closest alternatives when your route or market focus changes.
- Price Tracker API — choose it when the workflow should focus on price tracker api rather than this Actor's exact route.
- Flipkart Price Tracker — choose it when the workflow should focus on flipkart rather than this Actor's exact route.
- Amazon Price Tracker — choose it when the workflow should focus on amazon rather than this Actor's exact route.
Each related Actor uses its own verified country and platform enums. Choose by the marketplace you need rather than assuming every fixed edition supports the 23-route union.
Support
Get product guidance in the TrueFetch community, review the Store page, use the API page, or open an Issue with a reproducible input and run ID.
Run a bounded one-result test · Open the API reference
Last Updated: August 10, 2026