IndiaMART data API: buy leads, catalogs and supplier profiles
IndiaMART's data API is organized around the seller's GL account. The buy-lead feed pages through /v1/leads/search (offerId, offerTitle, glUserCity, eto_ofr_approx_order_value); spending a credit to unlock a buyer is /v1/leads/unlock. Catalog cards come from /v1/catalog/items, the prepaid wallet from /v1/wallet/credits, and company KYB fields from /v1/companies/lookup plus /v1/users/profile. Every call form-posts a shared app token with the seller's glusrid and an AK session key.
IndiaMART is India's largest B2B marketplace: manufacturers, wholesalers and MSME sellers open it to browse buy leads, unlock buyer contact details, manage product catalogs, and talk to enquiring companies. Its data API is organized around form-posted calls that carry a shared app token plus the seller's glusrid and an AK session key — covering the paginated buy-lead feed (offerId, offerTitle, glUserCity, eto_ofr_approx_order_value), GL user profiles (COMPANYNAME, GSTIN_number, TURNOVER), the prepaid lead-credit wallet (glusrCreditsAv, blAllocDaily, weeklyLapseDate), catalog items (pc_item_name, in_pc_item_fob_price), public company records (gstVerifiedFlag, legalStatus, yoe), and the lead-unlock call that spends a credit to reveal a buyer's mobile and email.
Screenshots
API surface
Display buy leads
POST
/v1/leads/searchopendataReturns the paginated buy-lead feed a seller sees on the BL list: requirement title, quantity, approximate order value, buyer city/company, GST-verified flag, and whether the lead has already been purchased.
Auth: Form fields app_token (shared app token), modid=ANDROID, glusrid, and AK session key; jwt_token on authenticated seller sessions.
- offerId
- offerTitle
- offerDescription
- offerQuantity
- offerVerified
- offerDateIst
- glUserName
- glUserCompany
- glUserCity
- glUserState
- glUserCountry
- glusrid
- fk_glcat_mcat_id
- prime_mcat_name
- eto_ofr_approx_order_value
- eto_ofr_buyer_gst_verified
- purchaseStatus
- memberSince
Illustrative example reconstructed from the app's interface — not a live capture.
POST /v1/leads/search HTTP/1.1 Content-Type: application/x-www-form-urlencoded app_token=<app-token>&modid=ANDROID&glusrid=95732645&AK=<session-key>&start=0&end=20{ "STATUS": "OK", "CODE": "200", "DATA": [{ "offerId": "2419087654", "offerTitle": "Industrial PVC Pipe 4 inch", "offerDescription": "Need 2000 pcs, ISI marked, delivery Delhi NCR", "offerQuantity": "2000 pcs", "offerVerified": "1", "offerDateIst": "2026-09-23 11:42:00", "glUserName": "Ravi Sharma", "glUserCompany": "NCR Polymers Pvt Ltd", "glUserCity": "New Delhi", "glUserState": "Delhi", "glUserCountry": "India", "glusrid": "81233421", "fk_glcat_mcat_id": "174", "prime_mcat_name": "PVC Pipes", "eto_ofr_approx_order_value": "250000", "eto_ofr_buyer_gst_verified": "1", "purchaseStatus": "0", "memberSince": "2018" }] }Derived from the app's interface; endpoint details are illustrative, not a live capture.
Reconstructed from the seller's buy-lead list flow.Field set matches the lead cards paged into the BL feed.
Seller / buyer profile
POST
/v1/users/profileosintLoads the logged-in (or looked-up) GL user record used by My Profile and BizFeed: name, company, GSTIN, membership type, geo, member-since date, and catalog logo.
Auth: Form fields app_token (shared app token), modid=ANDROID, glusrid, and AK session key.
- glusrid
- FIRSTNAME
- LASTNAME
- COMPANYNAME
- EMAIL1
- MOBILE1
- city
- cityid
- stateid
- GSTIN_number
- CUSTTYPE_NAME
- TURNOVER
- glusr_usr_logo_img_90x90
- glusr_usr_latitude
- glusr_usr_longitude
- glusr_usr_membersince
- glusr_listing_status_reason
Illustrative example reconstructed from the app's interface — not a live capture.
POST /v1/users/profile HTTP/1.1 Content-Type: application/x-www-form-urlencoded app_token=<app-token>&modid=ANDROID&glusrid=95732645&comp_logo=1&others=glusr_usr_latitude,glusr_usr_longitude,glusr_usr_membersince,glusr_listing_status_reason{ "glusrid": "95732645", "FIRSTNAME": "Anita", "LASTNAME": "Mehta", "COMPANYNAME": "Mehta Fasteners", "EMAIL1": "[email protected]", "MOBILE1": "9810012345", "city": "Ahmedabad", "cityid": "55", "stateid": "12", "GSTIN_number": "24AABCM1234P1Z5", "CUSTTYPE_NAME": "Paid", "TURNOVER": "2-5 Cr", "glusr_usr_logo_img_90x90": "https://cdn.example.com/logo.jpg", "glusr_usr_latitude": "23.0225", "glusr_usr_longitude": "72.5714", "glusr_usr_membersince": "2014-03-11", "glusr_listing_status_reason": "" }Derived from the app's interface; endpoint details are illustrative, not a live capture.
Reconstructed from the My Profile and BizFeed profile flow.Field set matches the GL user record bound to the profile screens.
Buy-lead credit wallet
POST
/v1/wallet/creditsopenfinanceReturns the seller's prepaid buy-lead credit wallet and weekly allocation/lapse counters that gate purchasing a lead from the BL list.
Auth: Form fields app_token (shared app token), modid=ANDROID, glusrid, and AK session key.
- STATUS
- CODE
- MESSAGE
- glusrCreditsAv
- blAllocDaily
- blAllocCreditCurweek
- blConsumeCreditCurweek
- blLapseCreditCurweek
- blPurchaseCount
- weeklyLapseDate
- yearlyLapsable
- weeklyExpAvai
- weeklyExpAlloted
- totalExpAvai
Illustrative example reconstructed from the app's interface — not a live capture.
POST /v1/wallet/credits HTTP/1.1 Content-Type: application/x-www-form-urlencoded app_token=<app-token>&modid=ANDROID&glusrid=95732645&AK=<session-key>{ "STATUS": "OK", "CODE": "200", "MESSAGE": "Success", "DATA1": { "glusrCreditsAv": "42", "blAllocDaily": "10", "blAllocCreditCurweek": "50", "blConsumeCreditCurweek": "8", "blLapseCreditCurweek": "0", "blLapseDaily": "0", "blPurchaseCount": "126", "weeklyLapseDate": "2026-09-28", "yearlyLapsable": "120" }, "DATA2": { "weeklyExpAvai": 18, "weeklyExpAlloted": 25, "weeklyExpDate": "2026-09-28", "hostingExpAvai": "4", "totalExpAvai": "22" } }Derived from the app's interface; endpoint details are illustrative, not a live capture.
Reconstructed from the daily business-summary wallet card.Counters match the weekly allocation and lapse display.
Product catalog listing
POST
/v1/catalog/itemsopendataLists a seller's (or searched) catalog items with display id, name, FOB price, MOQ, micro-category, and company glusrid — the same payload that fills My Products and search result cards.
Auth: Form fields app_token (shared app token), modid=ANDROID, glusrid, and AK session key.
- productListingStatus
- prod_det_displayID
- prod_det_detail_itemname
- pc_item_name
- prod_det_descsmall
- prod_det_price
- prod_det_currency
- in_pc_item_fob_price
- prod_det_prodSearchMinOrderQuantity
- prod_det_prodSearchMOQUnitType
- prod_det_mcat_id
- prod_det_mcat_name
- prod_det_cpnyname
- prod_det_glusr_id
- pc_item_status
Illustrative example reconstructed from the app's interface — not a live capture.
POST /v1/catalog/items HTTP/1.1 Content-Type: application/x-www-form-urlencoded app_token=<app-token>&modid=ANDROID&glusrid=95732645&start=0&end=20{ "productListingStatus": "OK", "products": [{ "prod_det_displayID": "DID-884210", "prod_det_detail_itemname": "SS 304 Hex Bolt M12", "pc_item_name": "SS 304 Hex Bolt M12", "prod_det_descsmall": "Fully threaded, DIN 933, MOQ 1000", "prod_det_price": "4.50", "prod_det_currency": "INR", "in_pc_item_fob_price": "4.50", "prod_det_prodSearchMinOrderQuantity": "1000", "prod_det_prodSearchMOQUnitType": "Piece", "prod_det_mcat_id": "1742", "prod_det_mcat_name": "Hex Bolts", "prod_det_cpnyname": "Mehta Fasteners", "prod_det_glusr_id": "95732645", "pc_item_status": "1", "prod_det_250_250": "https://cdn.example.com/bolt.jpg" }] }Derived from the app's interface; endpoint details are illustrative, not a live capture.
Reconstructed from the My Products and search-result card flow.Wire fields match the catalog item model behind product cards.
Company / supplier record
POST
/v1/companies/lookuposintFetches the public company card used on supplier/buyer profile screens: legal name, contact person, GST/verified flags, employee band, year of establishment, and PNS/WhatsApp numbers.
Auth: Form fields app_token (shared app token), modid=ANDROID, glusrid, and AK session key.
- glUserID
- glUserDisplayId
- dirSearchCompany
- dirSearchContactPerson
- dirSearchDesignation
- dirSearchCity
- dirSearchState
- dirSearchCountry
- dirSearchPin
- dirSearchAddress
- mobile
- whatsAppNumber
- gstVerifiedFlag
- verifiedSupplierFlag
- numberOfEmp
- yoe
- legalStatus
- biz
- companyLogo
Illustrative example reconstructed from the app's interface — not a live capture.
POST /v1/companies/lookup HTTP/1.1 Content-Type: application/x-www-form-urlencoded app_token=<app-token>&modid=ANDROID&glusrid=81233421&AK=<session-key>{ "glUserID": "81233421", "glUserDisplayId": "DID-11209", "dirSearchCompany": "NCR Polymers Pvt Ltd", "dirSearchContactPerson": "Ravi Sharma", "dirSearchDesignation": "Purchase Manager", "dirSearchCity": "New Delhi", "dirSearchState": "Delhi", "dirSearchCountry": "India", "dirSearchPin": "110020", "dirSearchAddress": "Okhla Industrial Area Phase 2", "mobile": "9810098765", "whatsAppNumber": "9810098765", "gstVerifiedFlag": "1", "verifiedSupplierFlag": "1", "numberOfEmp": "51-100", "yoe": "2009", "legalStatus": "Private Limited", "biz": "Manufacturer", "companyLogo": "https://cdn.example.com/ncr-logo.jpg" }Derived from the app's interface; endpoint details are illustrative, not a live capture.
Reconstructed from the supplier profile card flow.KYB flags match the verified-supplier badge logic.
Purchase a buy lead
POST
/v1/leads/unlockopenfinanceSpends one (or more) buy-lead credits to unlock the full buyer contact — mobile, email, company — and returns the remaining glusrCreditsAv balance.
Auth: Form fields app_token (shared app token), modid=ANDROID, glusrid, and AK session key; jwt_token on authenticated seller sessions.
- STATUS
- CODE
- MESSAGE
- offerId
- purchaseStatus
- glUserPhoneMobile
- glUserEmail
- glUserName
- glUserCompany
- glusrCreditsAv
Illustrative example reconstructed from the app's interface — not a live capture.
POST /v1/leads/unlock HTTP/1.1 Content-Type: application/x-www-form-urlencoded app_token=<app-token>&modid=ANDROID&glusrid=95732645&AK=<session-key>&offerId=2419087654{ "STATUS": "OK", "CODE": "200", "MESSAGE": "Lead purchased", "offerId": "2419087654", "purchaseStatus": "1", "glUserPhoneMobile": "9810098765", "glUserEmail": "[email protected]", "glUserName": "Ravi Sharma", "glUserCompany": "NCR Polymers Pvt Ltd", "glusrCreditsAv": "41" }Derived from the app's interface; endpoint details are illustrative, not a live capture.
Reconstructed from the lead-purchase confirmation flow.Returned balance matches the wallet counter shown after a purchase.
Data categories
- buy leads
- supplier profiles
- product catalog
- lead credits
- company records
Where teams use this data
Lead-desk CRM sync
A seller CRM pulls /v1/leads/search on a timer, maps offerId, offerTitle, glUserCity and eto_ofr_approx_order_value onto opportunity cards, then calls /v1/leads/unlock only when a scoring rule fires so credits are not spent on noise.
Catalog-to-ERP product feed
An ERP bot reads /v1/catalog/items and upserts pc_item_name, in_pc_item_fob_price, prod_det_prodSearchMinOrderQuantity and prod_det_mcat_name into the SKU master so storefront prices stay in lockstep with IndiaMART.
KYB enrichment on inbound enquiries
When a new enquiry arrives, a KYB service hits /v1/companies/lookup and /v1/users/profile for gstVerifiedFlag, GSTIN_number, legalStatus, yoe and TURNOVER before a sales agent is assigned.
Credit-wallet burn dashboard
Finance pulls /v1/wallet/credits nightly and charts glusrCreditsAv, blConsumeCreditCurweek and weeklyLapseDate so unused daily allocations are spent before they lapse.
Frequently asked questions
What does the IndiaMART data API cover?
Six resource groups: the paged buy-lead feed at /v1/leads/search, seller and buyer GL profiles at /v1/users/profile, the prepaid lead-credit wallet at /v1/wallet/credits, catalog items at /v1/catalog/items, public company records at /v1/companies/lookup, and the lead-unlock call at /v1/leads/unlock that reveals a buyer's contact details.
How are those calls authenticated?
Each form post carries a shared app token, the seller's numeric glusrid, and an AK session key; authenticated seller sessions also attach a jwt_token. The credit wallet and lead-unlock calls require an active seller session.
What fields identify a buy lead versus a catalog SKU?
A buy lead is keyed by offerId and includes offerTitle, glUserCity, eto_ofr_approx_order_value and purchaseStatus. A catalog SKU is keyed by prod_det_displayID / pc_item_name with in_pc_item_fob_price and prod_det_prodSearchMinOrderQuantity.
Can the credit wallet be read without purchasing a lead?
Yes. POST /v1/wallet/credits returns glusrCreditsAv plus the weekly allocation and lapse counters (blAllocDaily, blConsumeCreditCurweek, weeklyLapseDate) used by the daily business-summary screen.
Topics
- IndiaMART API
- buy leads API
- B2B marketplace data
- supplier profile fields
- glusrid
- product catalog API
- lead credits
- supplier verification API
Need this app's data API integrated?
We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.