IndiaMART Scraper

Collect Indian supplier listings by product category and city. One clean row per listing with price, company, location, years in business, ratings and product specs. No login and no API key.

What it does

• Price as a number, with the unit it is sold by, so you can sort and compare instead of reading text.
• Supplier details on every row: company name, their own website, city and locality, and how many years they have been in business, plus a flag showing whether the supplier is based in that city or merely serves it.
• Trust signals passed through as published: rating, number of ratings, response rate, and whether the supplier carries a verification badge.
• Product specifications as a structured field, so attributes like size, material and brand arrive ready to filter.
• Deduplicated across every category and city, so a listing that appears in two searches is delivered once and charged once.

Common uses: supplier discovery and sourcing, price benchmarking across cities, building a vendor database, import and export research, and lead lists of manufacturers and distributors.

Input

Field	Type	Description
categories	array	Category names as they appear in the site address, for example industrial-valves. Plain names like "ball valves" are converted for you.
cities	array	Cities such as mumbai or delhi. Leave empty to search all of India.
maxResultsPerCombination	integer	Cap per category and city pair. Default 50.
proxyConfiguration	object	Recommended for larger runs. See the note below.

Example input

{
  "categories": ["industrial-valves", "ball-valves"],
  "cities": ["mumbai", "delhi", "chennai"],
  "maxResultsPerCombination": 100
}

Output

Each item is one supplier listing.

{
  "id": "2853262556873",
  "title": "Industrial Butterfly Valve",
  "category": "industrial-valves",
  "price": 600.0,
  "priceLabel": "₹ 600",
  "priceUnit": "Piece",
  "currency": "INR",
  "company": "Acme Valves Private Limited",
  "companyWebsite": "https://example.com",
  "yearsInBusiness": 20,
  "tenureLabel": "20 yrs",
  "city": "Mumbai",
  "locality": "Andheri West",
  "isServiceArea": false,
  "searchCity": "mumbai",
  "rating": 3.7,
  "ratingCount": 85,
  "responseRate": 93,
  "hasTrustSeal": true,
  "isLeadingSupplier": false,
  "specs": { "Size": "25mm to 50mm", "Material": "Cast Iron", "Brand": "Acme" },
  "imageUrl": "https://example.com/photo.jpg",
  "url": "https://www.indiamart.com/proddetail/example-2853262556873.html"
}

Notes

• More cities is how you get more suppliers, not a bigger cap. Each category and city pair returns roughly 28 listings and that is all the source publishes for it. City pages barely overlap with each other, so two cities return close to two full sets of different suppliers. To collect a market, list many cities rather than raising the cap.
• Enable the proxy for larger runs. Sustained requests from a single address get throttled after roughly a dozen pages. The actor waits and retries automatically, and if a pair still cannot be fetched it is named in the log and counted, so a short run is never presented as a complete one.
• Listings that show "Ask Price" instead of a figure return null for price and keep every other field.
• rating, responseRate and the badges are only published for some suppliers. Newer sellers commonly have none, and those rows return null rather than a zero, which would read as a bad score rather than no score.
• locality is filled only when the listing states a neighbourhood as well as a city. Longer addresses such as "Area, Town, Dist. City" put the city in city and everything before it in locality.
• isServiceArea marks a different kind of result. Some listings say a supplier deals in a city rather than being based there. Those rows return the city with isServiceArea set to true, so you can tell a local supplier from one that merely covers the area. Filter it out if you only want businesses physically in the city.
• Prices are what the supplier advertises, usually a starting price, and are frequently negotiable for bulk orders. Treat them as a benchmark rather than a quote.

Found this useful? Leave a quick review. It takes a few seconds and it genuinely helps other people find the actor.

Privacy

To improve our actors we collect anonymized usage telemetry (run stats and input patterns). No personal account data is collected.