Mecverse Logo
Book demo
IndiaMART API guide

How IndiaMART leads reach your CRM.

IndiaMART gives paid sellers two ways to take leads out of Lead Manager: the Push API and the Pull API. Here is how each works, the limits that trip up most integrations, and the setup we use so no lead goes missing.

Checked against IndiaMART's Push API and Pull API documentation, November 2026.

Push API vs Pull API

Most sellers pick one. The reliable setup uses both: Push for speed, Pull to make sure nothing slipped through.

Comparison of the IndiaMART Push API and Pull API
AspectPush APIPull API
How leads arriveIndiaMART sends each lead to your HTTPS webhook as a JSON POST.Your system asks IndiaMART for the leads in a time window.
SpeedReal time.Once every 5 minutes at most.
Older leadsOnly leads that arrive after activation.Up to 365 days back, 7 days per request.
What you runA public HTTPS endpoint that answers with HTTP 200.A scheduled job holding the API key.
When it breaksIndiaMART retries. After 48 hours of continuous failure it switches Push off.More than 5 calls in a minute blocks the key for 15 minutes. A key unused for 7 days expires.
Use it forInstant replies and live routing.Backfill, reconciliation, and catching anything Push missed.

Switching on the Push API

The webhook URL must start with https:// and sit on a public domain. IndiaMART counts a push as delivered when your endpoint answers with HTTP 200, and keeps retrying until it does.

  1. 1

    Open Lead Manager

    Sign in at seller.indiamart.com with the paid seller account and open Lead Manager.

  2. 2

    Import/Export Leads

    From the ⋮ menu choose Import/Export Leads, then Push API.

  3. 3

    Pick your CRM

    Choose it from the list, or pick Other and enter a name and your https:// webhook URL.

  4. 4

    Confirm the OTP

    IndiaMART sends an OTP to the account's primary mobile. Push goes live once it is entered.

  5. 5

    Send a test lead

    Use the test option and check the API logs for “Lead sent successfully” with code 200.

What a lead looks like

Push and Pull return the same fields. Push sends one lead per request; Pull returns a list. Field names below are IndiaMART's; the values are made up.

{
  "CODE": 200,
  "STATUS": "SUCCESS",
  "RESPONSE": {
    "UNIQUE_QUERY_ID": "2938471650",
    "QUERY_TYPE": "B",
    "QUERY_TIME": "2026-11-12 11:42:08",
    "SENDER_NAME": "Rakesh Verma",
    "SENDER_MOBILE": "+91-98XXXXX421",
    "SENDER_EMAIL": "rakesh@example.com",
    "SUBJECT": "Requirement for SS 304 Pipe Fittings",
    "SENDER_COMPANY": "Verma Fabricators",
    "SENDER_CITY": "Ludhiana",
    "SENDER_STATE": "Punjab",
    "SENDER_PINCODE": "141003",
    "SENDER_COUNTRY_ISO": "IN",
    "QUERY_PRODUCT_NAME": "SS 304 Pipe Fittings",
    "QUERY_MESSAGE": "Need 500 pcs, 2 inch. Please share best price.",
    "QUERY_MCAT_NAME": "Stainless Steel Pipe Fittings",
    "CALL_DURATION": "",
    "RECEIVER_MOBILE": ""
  }
}
IndiaMART lead fields and how to use them
FieldsHow to use them
UNIQUE_QUERY_IDThe deduplication key. Store it on the CRM record and reject any lead you have already seen, whether it came by Push or Pull.
QUERY_TYPEWhich kind of lead this is. Drives the source label and whether an automatic reply goes out.
SENDER_NAME, SENDER_MOBILE, SENDER_EMAILThe contact. SENDER_NAME falls back to “IndiaMART Buyer” when the buyer has not shared a name, so don't put it in a greeting unchecked.
SENDER_COMPANY, SENDER_CITY, SENDER_STATE, SENDER_PINCODEThe account and the location. Use these for routing by region.
QUERY_PRODUCT_NAME, QUERY_MCAT_NAME, QUERY_MESSAGE, SUBJECTWhat the buyer wants. Use these for routing by product line and as the product variable in a WhatsApp template.
SENDER_MOBILE_ALT, SENDER_PHONE, SENDER_PHONE_ALT, SENDER_EMAIL_ALTExtra contact details, often empty. Keep them, but match repeat buyers on the primary mobile.
CALL_DURATION, RECEIVER_MOBILEFilled for PNS calls. Useful for reporting on which calls connected and for how long.

QUERY_TYPE: the five lead types

W
Direct enquiry
A buyer contacted you from your listing or catalog.
B
BuyLead
A requirement you consumed in Lead Manager. Other suppliers can consume it too.
P
PNS call
A call through IndiaMART's preferred number service that connected.
BIZ
Catalog view
Catalog-view BuyLeads you consumed, or catalog views after 7 days of no contact between you and that buyer.
WA
WhatsApp enquiry
A buyer who reached you through IndiaMART on WhatsApp.

Not in the API: call attempts that did not connect, repeat catalog views within 7 days, your replies and call-backs, buyer GST and trust details, and tenders.

Pull API rules that break integrations

Endpoint and key
Leads come from mapi.indiamart.com/wservce/crm/crmListing/v2/ with three parameters: glusr_crm_key, start_time and end_time. The key is generated under Import/Export Leads → Pull API, and only paid sellers see the Generate Key option.
Five minutes between calls
Calls closer than 5 minutes apart return 429. More than 5 calls in one minute blocks the key for 15 minutes.
Seven days per request, 365 days back
start_time and end_time can be at most 7 days apart, in IST. Data older than 365 days is not returned. With no dates, you get the last 24 hours, or everything since your last call if that was within 24 hours.
Keys expire quietly
A key not called for 7 days expires. Generating a new key stops the old one immediately. Leads from before key generation become available 24 hours after it.

Pull API response codes

IndiaMART Pull API response codes and what they mean
CodeWhat it means
200Leads returned for the window.
204No leads in the window, or leads from before key generation are not available yet.
400A date parameter is missing, or the window reaches back past 365 days.
401The key is wrong, has expired after 7 idle days, or was replaced by a newer key.
429Called within 5 minutes of the last call, or more than 5 calls in a minute (key blocked for 15 minutes).
500An error on IndiaMART's side. Retry on the next scheduled run.

How we build it so no lead goes missing

Acknowledge first, process second
Our webhook stores the lead and answers 200 straight away, then writes to your CRM and sends WhatsApp. A slow CRM never makes IndiaMART think the push failed.
Pull as a safety net
A scheduled Pull run every 10–15 minutes over a window that overlaps the last one. It catches anything Push missed and keeps the key from expiring.
One lead, one record
UNIQUE_QUERY_ID deduplicates across Push and Pull. The buyer's mobile number links repeat enquiries to the same contact.
Alerts long before 48 hours
If pushes start failing or the Pull key returns 401, we are alerted and fix it well before IndiaMART's 48-hour cut-off switches Push off.

Rather not run the webhook yourself?

We set up Push and Pull, map leads into your CRM, and reply to buyers on WhatsApp. Integration starts at ₹10,000.

See the IndiaMART integration service →

IndiaMART API questions

Is the IndiaMART API free?
The Push and Pull APIs are available to paid IndiaMART sellers. IndiaMART describes the Leads API as an add-on to a seller package, not something sold on its own, and does not publish a separate price for it.
Why does my IndiaMART Pull API return error 429?
Either you called within 5 minutes of the previous call, or you made more than 5 calls in one minute, which blocks the key for 15 minutes. Schedule calls at least 5 minutes apart.
Why did my IndiaMART Pull API key stop working?
Keys expire after 7 days without a call, and generating a new key stops the old one. Both return 401. Generate a key, update it everywhere it is used, and keep a schedule that calls it regularly.
Can I get leads from before I switched on the Push API?
Not through Push. Use the Pull API to fetch them, up to 365 days back and 7 days per request.
Does the IndiaMART API include the buyer's GST number or rating?
No. GST and trust details such as ratings and call response rate stay in Lead Manager. Call attempts that did not connect, your replies and call-backs, and tenders are also not in the API.
Should I use the Push API or the Pull API?
Both. Push gives you the lead in real time so you can reply first. Pull, run on a schedule, backfills history and catches anything Push missed. Deduplicate on UNIQUE_QUERY_ID.