IndiaMART Supplier Data, One Scraping API
IndiaMART is a large B2B marketplace where supplier listings, product catalogs, minimum order quantities, prices and contact details sit on public pages.
Collecting that information at scale means dealing with JavaScript rendering, proxy rotation and bot detection. A hosted scraping API lets you send a target URL and receive parsed HTML or structured JSON, so your team can focus on the data rather than the browser fleet.
What the API does with an IndiaMART page
You pass a public IndiaMART URL to the endpoint along with your API key. The service renders the page, including its JavaScript, rotates proxies and returns the result as parsed HTML or structured JSON. Optional parameters let you control rendering, proxy type, country targeting and extraction rules. The service is designed for public pages only; content behind a login is outside its scope.
Three common IndiaMART collection tasks
Most teams approach IndiaMART for one of three reasons. Procurement research needs supplier names, product catalogs and minimum order quantities across a category. Pricing work needs unit prices to compare market positioning. Partnership or sourcing work needs supplier contact details. Each task maps to fields that appear on public supplier and product pages, and each can be requested through the same endpoint with different extraction rules.
Fields you can expect from a public IndiaMART page
A public IndiaMART page typically exposes supplier name, product catalog, minimum order quantity, unit price, location, contact details and supplier rating. Which of these appear depends on the page type and how the page is rendered. When you already know the page structure, map each field to a CSS selector through extract_rules. When you would rather describe the fields in natural language and let the service locate them, use ai_extract_rules. Either route returns structured JSON, so the choice is really about whether your selectors are stable or your field definitions are easier to state in words.
Request options and what they change
The endpoint accepts several parameters that affect rendering, network path and output. render_js enables JavaScript execution for pages that build content client-side. stealth_proxy routes the request through a stealth proxy for pages with aggressive bot detection. country_code targets a specific country. extract_rules and ai_extract_rules control how structured data is pulled from the rendered page. These options are independent: you can combine rendering with proxy choice, and extraction with either.
How credits are consumed
A plain request costs one credit. Enabling JavaScript rendering costs five credits per successful request. Premium proxies cost ten credits without JavaScript rendering or twenty-five with it. A stealth proxy request costs seventy-five credits. These figures are the total per-request cost for each option, not add-ons on top of a base credit. Credits are valid for one month and do not roll over.
Plan comparison
The table below preserves the published plan rows, including monthly price, API credits, concurrent requests and feature availability. Prices are exclusive of VAT. Use the table to compare the credit allowance against your expected request mix; a plan with more credits but the same concurrency may still be the right fit if your workload is steady rather than bursty.
Decision checklist before you build
Use this checklist to decide whether a hosted API fits your IndiaMART task. First, confirm the pages you need are public and do not require a login. Second, check whether the fields you need are rendered by JavaScript; if so, plan for render_js and the associated credit cost. Third, estimate your request volume and compare it with the credit allowance on the plan you are considering. Fourth, decide whether you need structured output via extract_rules or ai_extract_rules, or whether parsed HTML is enough. Fifth, review the target site's terms of service before deploying. If your volume is small and the pages are static, a simpler direct fetch may be sufficient; the hosted API is most useful when rendering, proxy rotation and bot handling would otherwise require significant engineering effort.
Distinguishing common failure modes
When a request does not return the expected data, the cause usually falls into one of three categories. Anti-bot blocking shows up as a challenge page or an empty response; enabling stealth_proxy is the usual remedy. JavaScript-rendered content that is missing from the response usually means render_js was not enabled. Selector or extraction mismatches produce JSON with missing or null fields even though the page rendered; in that case, review your extract_rules selectors or switch to ai_extract_rules. Separating these causes avoids spending credits on the wrong fix.
Worked example: a public supplier page
Suppose you want to collect supplier name, product catalog, minimum order quantity, unit price, location and contact details from a public IndiaMART supplier page. You send a GET request with the page URL, your API key, render_js enabled and an extract_rules object that maps each field to a CSS selector. The service renders the page, rotates proxies and returns JSON with the requested fields. If the page's structure changes and selectors stop matching, you can replace extract_rules with ai_extract_rules describing the same fields in natural language. This example uses only fields that appear on public pages; it does not assume access to login-protected content.
Legal and compliance notes
Public-facing pages can usually be scraped, but you should review the target site's terms of service before deploying and avoid post-login content. The service does not collect or store personal data from scraped sites unless the user explicitly requests it. Compliance with GDPR and CCPA depends on how you use the data you collect, so treat the API as a transport layer and apply your own data-handling policies.
| Plan | Monthly price | API credits | Concurrent requests | JavaScript rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
All prices are exclusive of VAT. Plan rows are a dated reference; check current pricing before purchase.
Frequently asked questions
Do I need an account to scrape IndiaMART?
No external IndiaMART account is required. You sign up for an API key, which includes 1,000 free credits and does not require a card. You then send the target URL and the service handles rendering and proxy rotation.
Is scraping IndiaMART legal?
Public-facing pages can usually be scraped, but you should review the target site's terms of service before deploying and avoid post-login content. Legality also depends on how you use the collected data, so apply your own compliance review.
What data can I extract from IndiaMART?
The scope is limited to content visible on the public page. You can define fields yourself with extract_rules and CSS selectors, or describe them in plain language and let ai_extract_rules handle AI-driven extraction; either path returns structured JSON. Common targets are supplier name, product catalog, minimum order quantity, unit price, location, contact details and supplier rating.
How do I start scraping IndiaMART?
Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies and returns the data. The 1,000 free credits let you test before committing to a paid plan.
Will I get blocked when scraping IndiaMART?
The service rotates residential proxies and uses a real headless browser so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request to route through a stealth proxy.
How much does it cost to scrape IndiaMART?
Signup includes 1,000 free credits with no card required. Paid plans start at $19 per month for higher volume and concurrency. Credit cost per request depends on options: five credits for JavaScript rendering, twenty-five for a premium proxy with JavaScript rendering, and seventy-five for a stealth proxy.