How to Get IndiaMART Leads into Your CRM
IndiaMART has no Excel export for enquiries, so the reliable way to move leads into a CRM is its Push or Pull API. How each works, who can use them, the fields you get, the limits, and how to avoid duplicates.
Written by Qualimize Team
Founder, Qualimize
- Published
- Last updated
- Reading time
- 10 min read
Table of contents
- 01 The short answer
- 02 Why IndiaMART leads slip through the cracks
- 03 Option 1: the Push API (real time)
- 04 Option 2: the Pull API (scheduled fetch)
- 05 What data you get, and how to map it
- 06 Avoiding duplicate IndiaMART leads
- 07 Working IndiaMART leads once they are in the CRM
Full article
The short answer
To get IndiaMART leads into your CRM, use IndiaMART's Lead Manager CRM API: either the Push API, which sends each enquiry to your CRM's webhook URL in real time, or the Pull API, which lets your CRM fetch enquiries with a key at intervals. IndiaMART's own help centre says there is no option to export enquiries to Excel, and both APIs are available only to paid sellers as an add-on.
In practice that leaves three routes: a CRM that already has an IndiaMART connector, a middleware tool that calls the API for you, or your own small integration. All three use the same two APIs underneath, so the choices below about Push versus Pull, field mapping and duplicates apply whichever you pick.
Why IndiaMART leads slip through the cracks
IndiaMART enquiries arrive in Lead Manager, in the seller app, by SMS and email, and as phone calls. For an owner handling everything personally that can work. Once there are two or three salespeople, nobody is sure who replied to which buyer, and a manufacturer in Rajkot can end up with the same enquiry called twice and another not called at all.
The bigger problem shows up when IndiaMART is one source among several. If Meta ad leads live in a CRM and IndiaMART leads live in Lead Manager, you cannot compare the two channels on what matters: how many enquiries became quotes and orders, and what each order cost you. Bringing both into one pipeline is what makes that comparison possible.
Because IndiaMART does not offer a spreadsheet export, a CSV import is not a dependable fallback either. The API is the supported path.
Option 1: the Push API (real time)
With the Push API, IndiaMART calls your CRM. You give IndiaMART a webhook URL, and every new enquiry is sent there as an HTTPS POST with a JSON body. This is the route IndiaMART describes as delivering leads in real time, and it is the right default for a sales team where calling quickly matters.
To switch it on, open Lead Manager, use the three-dots menu, choose Push API under Import/Export Leads, pick your CRM from the list or choose Other and enter its name and webhook URL, then confirm with the OTP sent to your primary mobile number. IndiaMART provides a test option so you can send a sample lead to the URL before relying on it.
Two behaviours are worth knowing. IndiaMART treats a lead as delivered only when your URL answers with HTTP 200, and retries failed leads at regular intervals; you can see failures and retry counts in its failure logs. And if your CRM refuses leads continuously for more than 48 hours, IndiaMART deactivates the Push API, so a broken URL over a long weekend can switch the integration off.
- Push only covers enquiries received after activation; older leads need the Pull API
- There is no stated limit on the number of leads pushed
- IndiaMART says integration is do-it-yourself; its team does not build it for you
Option 2: the Pull API (scheduled fetch)
With the Pull API, your CRM calls IndiaMART. You generate a CRM key in Lead Manager, and the integration requests enquiries for a time window by passing the key with a start_time and end_time. With no times, it returns the last 24 hours.
The limits shape how you build it. The window can be at most 7 days per request. Consecutive calls should be at least 5 minutes apart, and more than 5 calls in a minute blocks the key for 15 minutes. IndiaMART's documentation describes polling every 5 to 15 minutes, with each request's start_time set a few minutes before the previous end_time so nothing falls between calls. The API returns at most the last 365 days of data, and enquiries from before the key was generated become available about 24 hours after you generate it.
Keys need care. A Pull key expires if it is not used for 7 days, and generating a new key immediately invalidates the old one, so two tools sharing one account can knock each other off. Treat the key like a password: keep it in your CRM's settings, never in a shared sheet or a screenshot.
Pull is the right choice for back-filling history after you first connect, and as a safety net that catches anything the Push API missed during an outage. Because overlapping windows return the same enquiry more than once, de-duplication is not optional with Pull.
What data you get, and how to map it
Both APIs return the same core fields for each enquiry. Map them once, carefully, and every IndiaMART lead will look like every other lead in your CRM. The table below lists the ones a sales team usually needs.
QUERY_TYPE tells you what kind of enquiry it was: W for a direct enquiry, B for a Buy-Lead, P for a PNS call, BIZ for a catalogue view and WA for a WhatsApp enquiry. Save it as a tag or field, because these behave very differently; a direct enquiry with a message is usually warmer than a catalogue view.
Some things never come through the API. IndiaMART's documentation says GST details and buyer trust information such as ratings and call response rate are shown only in Lead Manager, and some interactions are excluded: call attempts that did not connect, replies and callbacks from either side, and catalogue views within 7 days of an existing conversation with that buyer. If your reps rely on those, they will still open Lead Manager for them.
Avoiding duplicate IndiaMART leads
Every enquiry carries a UNIQUE_QUERY_ID, and IndiaMART recommends using it to avoid duplicate data. Store it on the lead and have your integration skip any enquiry whose ID already exists. This is what makes it safe to run Push and Pull together, or to re-run a Pull window after an outage.
UNIQUE_QUERY_ID only catches the same enquiry twice. The same buyer sending two enquiries, or enquiring on IndiaMART after also filling a Meta lead form, needs a second check on phone number and email. Flag those as possible duplicates for a person to review rather than merging them automatically; a repeat buyer asking about a new product is a different opportunity.
Example: a Surat textile supplier runs Push for live leads and a Pull job every 15 minutes covering the last 20 minutes. During a 2-hour CRM outage, Push retries some enquiries and Pull picks up the rest. Both arrive with the same UNIQUE_QUERY_IDs, the integration keeps one copy of each, and no enquiry is lost or doubled. The setup is illustrative, not a customer case.
Working IndiaMART leads once they are in the CRM
Getting the lead in is half the job. Set auto-assignment by lead source so IndiaMART enquiries go to the reps who handle B2B buyers, use statuses that match your sales steps (contacted, quote sent, sample sent, order), and give every new enquiry a follow-up date.
Then report by source. Compare IndiaMART with Meta ads and your website on qualified leads and orders, not only enquiry counts. In Qualimize, IndiaMART lead sync is available on request and is switched on per workspace; once on, those leads sit in the same pipeline as Meta and website leads, can be auto-assigned by lead source, and show up in analytics by source.
- Assign IndiaMART leads automatically, by source, the moment they arrive
- Tag the QUERY_TYPE and product so reps see what the buyer asked about
- Set a follow-up on every enquiry; overdue lists catch the ones that slip
- Compare channels on qualified leads and orders, not enquiry volume
Comparison tables
IndiaMART Push API vs Pull API
| Factor | Push API | Pull API |
|---|---|---|
| Who calls whom | IndiaMART posts each lead to your webhook URL | Your CRM requests leads from IndiaMART with a key |
| Speed | Real time | As often as you poll; at least 5 minutes between calls |
| Past leads | Only enquiries after activation | Up to the last 365 days, 7 days per request |
| Failure handling | IndiaMART retries until it gets HTTP 200; deactivated after 48 hours of continuous failure | Your job: overlap windows and re-run missed periods |
| Key or setup risk | URL must stay up | Key expires after 7 days unused; a new key invalidates the old one |
| Eligibility | Paid IndiaMART sellers, as an add-on | Paid IndiaMART sellers, as an add-on |
| Best use | Live lead delivery | Back-filling history and catching gaps |
Mapping IndiaMART fields to CRM fields
| IndiaMART field | What it holds | Suggested CRM field |
|---|---|---|
| UNIQUE_QUERY_ID | The enquiry's unique ID | External ID, used for de-duplication |
| QUERY_TIME | When the enquiry was received | Lead created date |
| QUERY_TYPE | W, B, P, BIZ or WA | Tag or enquiry type field |
| SENDER_NAME / SENDER_COMPANY | Buyer's name and company | Name and company |
| SENDER_MOBILE / SENDER_EMAIL | Buyer's main contact details | Phone and email |
| SENDER_CITY / SENDER_STATE | Buyer's location | City and state, useful for territory assignment |
| QUERY_PRODUCT_NAME / SUBJECT | What the buyer asked about | Product or interest field |
| QUERY_MESSAGE | The buyer's message | First note on the lead |
FAQ
Can I export IndiaMART leads to Excel?
Not from IndiaMART itself. Its help centre says Lead Manager has no provision for exporting or downloading enquiries to a spreadsheet or Excel. The supported way to move enquiries out is the Lead Manager CRM API (Push or Pull), which a CRM or middleware tool can then save wherever you need. Be careful with unofficial browser extensions that claim to export leads, since they need access to your account.
What is the difference between IndiaMART Push API and Pull API?
With Push, IndiaMART sends each new enquiry to your CRM's webhook URL in real time and retries if it fails. With Pull, your CRM asks IndiaMART for enquiries in time windows of up to 7 days, no more often than every 5 minutes. Push is better for live leads; Pull is useful for history and as a backup.
How do I get my IndiaMART CRM key?
Paid sellers generate it inside Lead Manager, from the CRM integration or Import/Export Leads options in the three-dots menu. The key expires if unused for 7 days, and generating a new one immediately invalidates the old one, so update every tool that uses it. Keep it private, like a password.
Is IndiaMART CRM integration free?
The Lead Manager CRM API is available only to paid IndiaMART sellers, and IndiaMART describes it as an add-on that cannot be bought on its own. The integration itself is do-it-yourself; IndiaMART does not build it for you. Your CRM or middleware may also charge for its connector, so check both sides.
Why am I getting duplicate IndiaMART leads in my CRM?
Usually because Pull windows overlap, both Push and Pull are on, or a failed Push was retried. Store each enquiry's UNIQUE_QUERY_ID and skip any you already have, as IndiaMART recommends. Separately, flag leads with the same phone or email as possible duplicates for review, because the same buyer can send several genuine enquiries.
Where does Qualimize fit?
Qualimize is a CRM built for Meta lead ads, with IndiaMART lead sync available on request per workspace. It suits businesses that get leads from both Meta ads and IndiaMART and want them in one pipeline with auto-assignment by source and reporting by source. If IndiaMART is your only channel and you need GST or buyer trust details in the CRM, those stay in IndiaMART's Lead Manager whichever CRM you use.
Key takeaways
- IndiaMART has no Excel export for enquiries; the supported route into a CRM is the Lead Manager CRM API.
- Push sends leads to your webhook in real time and retries until it gets HTTP 200; Pull fetches up to 7 days per request, at least 5 minutes apart.
- Both APIs are an add-on for paid IndiaMART sellers, and the integration is do-it-yourself.
- Store UNIQUE_QUERY_ID on every lead to make Push, Pull and retries safe together.
- Put IndiaMART leads in the same pipeline as Meta and website leads, and compare channels on orders, not enquiry counts.