Integration of IndiaMART’s Lead Manager CRM API Version 2 with Third Party CRMs

This document contains the detailed steps for integration with CRM API Version 2.

If you are using the older version of the API (Version 1), please refer to the following document for integration : https://help.indiamart.com/knowledge-base/lms-crm-integration/

Purpose of IndiaMART CRM API

IndiaMART CRM API is a service that provides details of the business leads received through the IndiaMART portal in a JSON format, which is  suitable for pulling this data into a software of the client’s choice. The output of this API is not in a human-readable format and cannot be directly imported into MS-Excel. Also, this API is provided in DIY (Do it Yourself) mode, thus IndiaMART’s Technical Team won’t do any hand-holding in the integration with the API.

Any client who is registered as a Paid Seller on the IndiaMART platform and is using any third-party CRM or has an in-house CRM software can use the feature of API integration.

For using this API, the Client’s Technical Software / IT Team or the CRM Vendor should go through the detailed steps of integration explained in this document.

IndiaMART recommends its sellers to use IM Lead Manager to track, manage, follow-up, and communicate with their leads for better reliability, trust, and security concerns. There is no need to spend additional money on purchasing third-party CRM. Moreover, there are some additional data fields that are available only in the Lead Manager and not in the API output.

If your External CRM is configured for integration with the previous version of the CRM API, the integration with the Version 2 key will not work. For this, you can ask your CRM Vendor to implement integration with this version of the API.

A good software technical knowledge is required for the API integration process.

Steps of Integration

Step 1: Generate CRM Key

Step 2: Prepare your API URL

Examples of API Integration URLs

Step 3: Check API functionality

Sample API Response

Output Parameter details

Points to remember while using this API and output

Suggested API Hit strategy

CRM API Hit Logs

Security Warning

API Error messages

Advanced Troubleshooting

Frequently Asked Questions(FAQs)

Steps of Integration

Please find below the details and steps for integrating this API with third-party CRM to fetch IndiaMART leads (requires a paid account of IndiaMART).

Step 1: Generate CRM Key

Visit seller.indiamart.com, login to your account, then go to the Lead Manager and under the three dots menu ( ⋮ ) click on CRM Integration.

Or you can also directly go to Key Generation Page using the following link: https://seller.indiamart.com/leadmanager/crmapi.

Now, click on Generate Key. A unique CRM key will be generated and will also be sent to the registered email-id.

Note: In case you have already generated the CRM key, you can refer to the same from your email or check the key generation screen for your active CRM key. The CRM key will expire if it is not used in the last 15 days. On clicking ‘Generate Key’, a new key will be generated & the older one will expire (if any key was already generated earlier, it will stop working).

Step 2: Prepare your API URL

To prepare an API URL, we need to have the CRM key generated from Step 1.

There are three input parameters (marked in bold and italic) as given in the example URLs below.

Please replace the value of these 3 parameters with the required details:

1. glusr_crm_key: This is a unique API Key that is received on your primary email. This is also a mandatory input parameter.
2. start_time: This is the start date/time starting from which you wish to fetch the leads.
3. end_time: This is the end date/time till which you wish to fetch the leads.

start_time and end_time can be entered in the following two formats (Time is in IST):

• Date format (DD-MON-YYYY format) e.g. 01-Jan-2022
• Timestamp format (DD-MM-YYYYHH:MM:SS) e.g. 01-01-202216:30:00

Then as per the requirement, you can use any one of the URL formats given below to fetch data of IndiaMART leads.

Examples of API Integration URLs

(following URLs are just for demonstration purpose)

a) To get the IndiaMART leads between two given dates:

Note: Maximum allowed difference between start_time and end_time is 7 days

https://mapi.indiamart.com/wservce/crm/crmListing/v2/?glusr_crm_key=gIhfk7cDWoxdqBeFv+sb7kevHW7O1Axy&start_time=01-Jan-2022&end_time=06-Jan-2022

This URL will give data between 1st Jan and 6th Jan 2022 IST (midnight to midnight).

b) To get IndiaMART leads between two given timestamps

https://mapi.indiamart.com/wservce/crm/crmListing/v2/?glusr_crm_key=gIhfk7cDWoxdqBeFv+sb7kevHW7O1Axy&start_time=01-Jan-202209:00:00&end_time=06-Jan-202213:00:00

This URL will give data between 09:00 AM 1st Jan 2022 to 1:00 PM 6th Jan 2022 IST.

c) To fetch new leads received after the last API hit  (within the last 24 hours), do not mention the start and end dates in the URL:

https://mapi.indiamart.com/wservce/crm/crmListing/v2/?glusr_crm_key=gIhfk7cDWoxdqBeFv+sb7kevHW7O1Axy

API request made without the start and end dates returns the data for last 24 hours from the current time, and if the API was previously called in the last 24 hours, then data from the last access time of the API will be returned. For example: If the last API call was made at 10:30 am 19-Jan-2022 and then the API is again called at 11:30 am 19-Jan-2022 without the date parameters, the new leads from 10:30 am to 11:30 am will be fetched in this case.

Step 3: Check API functionality

Copy and paste the API URL prepared as mentioned in step 2, in any web browser (Google Chrome, Mozilla Firefox, etc.) to check if API URL is working correctly or not. Remember that the API would give an error message if you hit the API URL more than once in 5 minutes.

If the data is displayed in JSON format (refer to sample API response output below), this means the API is working fine. Now connect with your third-party CRM Service provider to integrate it into your CRM based on your requirements.

Sample API Response

Input: Enter your prepared API URL mentioned below in browser (Google Chrome / Mozilla Firefox / Microsoft Edge or any other Browser) and replace the Bold and Italics marked values

https://mapi.indiamart.com/wservce/crm/crmListing/v2/?glusr_crm_key=gIhfk7cDWoxdqBeFv+sb7kevHW7O1Axy&start_time=07-Dec-202109:00:00&end_time=08-Dec-202123:00:00

Sample API response Output (in JSON format):

{
“CODE”: 200,
“STATUS”: “SUCCESS”,
“MESSAGE”: “”,
“TOTAL_RECORDS”: 18,
“RESPONSE”:[
  {
   “UNIQUE_QUERY_ID”: “2012487827”,
   “QUERY_TYPE”: “W”,
            “QUERY_TIME”: “2021-12-08 12:47:25”,
            “SENDER_NAME”: “Arun”,
            “SENDER_MOBILE”: “+91-999XXXXXXX”,
            “SENDER_EMAIL”: “arunxyz@gmail.com”,
            “SENDER_COMPANY”: “Arun Industries”,
            “SENDER_ADDRESS”: “Arun Industries, Meerut, Uttar Pradesh, 250001”,
            “SENDER_CITY”: “Meerut”,
            “SENDER_STATE”: “Uttar Pradesh”,
            “SENDER_COUNTRY_ISO”: “IN”,
            “SENDER_MOBILE_ALT”: null,
            “SENDER_EMAIL_ALT”: “arunxyz1@gmail.com”,
            “QUERY_PRODUCT_NAME”: “Dye Sublimation Ink”,
            “QUERY_MESSAGE”: “I want to buy Dye Sublimation Ink.”,
            “CALL_DURATION”: null,
            “RECEIVER_MOBILE”: null
  }

If on hitting API in the browser, this data is fetched as shown above (in JSON format) then it means that API is working fine.

Output Parameter details:

Output parameters received after hitting the integration URL are mentioned below:

Points to remember while using this API and output:

1. The maximum allowed difference between start_time and end_time is 7 days. In case the difference is greater than 7 days, then the API will return an error message.



2. The minimum time difference between two consecutive hits should be 5 minutes. If the URL is hit more than once within 5 minutes, then the API will return an error message.
3. If there are more than 5 hits in a minute, then the CRM Key will be blocked for 15 minutes and the API will return an error message. 
4. At any particular instance, this API will only return the data for the last 365 days from the date of calling. For example, if the API is called on 1st March 2022, then data before 1st March 2021 will not be available. 
5. The previous data before the key generation time will be available after 24 hours. For example, if the key was generated on 1st Feb at 10 AM then the data before this time will be available from 2nd Feb 10 AM, however, you can start the integration to fetch the new leads after the key is generated.
6. Tenders data is not available through the API.
7. The CRM key will expire in case there is no user activity through the generated CRM key in the last 15 days. In such case, you must generate the CRM key again.
8. The Output of the API will be in JSON format. Your selected 3rd party CRM should be able to use the JSON data in their CRM.
9. If you are integrating this API URL with CRM, then UNIQUE_QUERY_ID can be used as a unique identifier to remove duplicate data in case the subsequent API calls are having overlapping date ranges. If a Buyer had sent two Enquiries and had made a call, the API will return 3 records for it, indicating three leads with different  UNIQUE_QUERY_ID. If you wish to combine them as a single record at your end, you may further apply merging logic with the combination of SENDER_MOBILE+SENDER_EMAIL.
10. This is not a push data-based API, instead it is a pull mechanism-based API i.e. the user has to hit the API for fetching data at scheduled intervals. We advise scheduling the data fetch every 10 -15 minutes (minimum allowed difference is 5 minutes). Your program should note the last end_time. Then the next API Call may have start_time set to previous end_time and new end_time as current System Time.
11. Keep your Server’s System time automatically synchronized with a reputed NTP Server (Network Time Protocol). You may use any of the Google public NTP Servers: time.google.com, time1.google.com, time2.google.com, time3.google.com, time4.google.com.
12. At times the output field QUERY_MESSAGE may contain these special characters:

1. \n - newline
2. \t - tab space
3. \r - carriage return
4. \b - backspace
5. \\ - backslash

It may also contain some Unicode (like â). It may also contain text in vernacular scripts (like आवश्यकता).

Suggested API Hit strategy

Strategy-1: Our advice is to call the API after every 5 minutes. Set the Start_Time with the previous End_Time of the last call and set the End_Time with the current time. It’s better to use the date-time range format like Start_Time/01-SEP-202009:00:00/End_Time/01-SEP-202013:00:00/ instead of the date range format.

For example:

1st call was at 16:00:00 with Start_Time/01-Jan-202215:55:01/End_Time/01-Jan-202216:00:00/

Then make the 2nd call at 16:05:00 with Start_Time/01-Jan-202216:00:01/End_Time/01-Jan-202216:05:00/This Strategy has a possibility of missing data between the milliseconds of 16:00:00 and 16:00:01. And also, some data may be missed which was generated at say 15:59:58 but finally got saved at 16:00:01. These are very rare boundary cases but can happen at times. –formatting

Strategy-2: Our best advice is to call the API every 5 minutes with a start_time of 5 minutes prior to the previous end_time and end_time as the current time.

For example:

1st call was at 16:00:00 with start_time=01-Jan-202215:50:00&end_time=01-Jan-202216:00:00

Then make the 2nd call at 16:05:00 with start_time=01-Jan-202215:55:00&end_time=01-Jan-202216:05:00.
In this strategy, we are using a rolling overlap of 5 minutes to cover up any missed boundary cases. However, due to this overlap, you would get some data duplicity, which can be easily eliminated with the help of  UNIQUE_QUERY_ID.

Final verdict: Strategy 2 is better. 

Also, we advised earlier to keep your Server’s Clock synchronized through a reliable Public NTP Service.

CRM API Hit Logs

The Logs tab on the key generation screen gives information on all the CRM API requests made in the last 15 days. These logs are available for Version 2 API integration only and will be visible after the key for this version is generated. The information available on this screen includes the details of the API hit time, the start and end date parameters, the number of leads returned, and the status message.

These logs will be helpful in debugging issues related to integration like data discrepancy in fetching leads, integration with wrong API key, etc.

Security Warning:

Please be careful that the CRM-API-Key (glusr_crm_key=gIhfk7cDWoxdqBeFv+sb7kevHW7O1Axy) is a Secret Key to get your Lead data from IndiaMART, if it is leaked or shared with anyone else, then all the data related to your leads could be easily accessed.

API Error messages:

In case you are getting output JSON as shown below:

1.{“CODE”:429,”STATUS”:”FAILURE”,”MESSAGE”:”It is advised to hit this API once in every 5 minutes,but it seems that you have crossed this limit. Please try again after 5 minutes.”,”TOTAL_RECORDS”:0,”RESPONSE”:[]}

Possible Causes

Check if the API URL is being called multiple times within 5 mins. Please note that this URL will provide data only once in every 5 minutes. 

2.{“CODE”:401,”STATUS”:”FAILURE”,”MESSAGE”:”CRM key that you are using is incorrect. Kindly use the correct CRM key as provided in the email.”,”TOTAL_RECORDS”:0,”RESPONSE”:[]}

Possible Causes

Please cross-check the CRM key. This should exactly be the same as mentioned in step 2

3. { “CODE”:401,”STATUS”:”FAILURE”,”MESSAGE”:”CRM key that you are using has expired as it was no longer in use. Kindly generate the new CRM key and use the new CRM key in API URL”,”TOTAL_RECORDS”:0,”RESPONSE”:[]}

Possible Causes

The CRM key will expire in case there is no user activity through the generated CRM key in the last 15 days. In such cases, you must generate the CRM key again. Or you may have generated a new key but are still using the old key.

4.{“CODE”:204,”STATUS”:”FAILURE”,”MESSAGE”:”There are no leads in the given time duration. Please try for a different duration.”,”TOTAL_RECORDS”:0,”RESPONSE”:[]}

Possible Causes

Please check with the different date range as there are no leads available for the time range mentioned in the URL.

5.{“CODE”:401,”STATUS”:”FAILURE”,”MESSAGE”:”CRM key that you are using has expired as it was no longer in use. Kindly use

the new key which you have generated on ’23-07-2021′ Check your email or SMS for the new key.”,”TOTAL_RECORDS”:0,”RESPONSE”:[]}

Possible Causes

Please cross-check the CRM key as the CRM key you are using has expired. The CRM key expires when a new key is generated from the seller portal.

6.{“CODE”:429,”STATUS”:”FAILURE”,”MESSAGE”:”Too Many  Requests”,”APP_AUTH_FAILURE_CODE”:429,”unique_id”:””}

Possible Causes

If there are  more than 5 CRM API requests in a minute, the CRM key will be disabled for 15 minutes for that user. Please wait for 15 minutes to again use the key.

7.{“CODE”:400,”STATUS”:”FAILURE”,”MESSAGE”:”You can fetch the data for the last 365 days only. Kindly change the Start Time or End Time accordingly”,”TOTAL_RECORDS”:0,”RESPONSE”:[]}

Possible Causes

Please check if the date range mentioned is correct. The CRM API only allows to fetch data for the last 365 days from key generation time, please try to fetch data within the allowed range.

8.{“CODE”:204,”STATUS”:”FAILURE”,”MESSAGE”:”Leads before 25-02-2022 12:57:54 will be available after 24 hours from the CRM key generation time. However, you can start the integration and fetch new leads.”,”TOTAL_RECORDS”:0,”RESPONSE”:[]}

Possible Causes

Check if you are trying to fetch data older than the CRM Key generation time. That data will be available after 24 hours. For example, if the key is generated on 28-12-2021 at 10 AM the data previous to this date will be available from 29-12-2021 at 10 AM.

9.{“CODE”: 400,  “STATUS”: “FAILURE”,”MESSAGE”: “Please enter both the date parameters start date and end date”,”TOTAL_RECORDS”: 0, “RESPONSE”: []}

Possible Causes

Please check if either start_time or the end_time parameter is missing in the API URL.

10.{“CODE”: 401, “STATUS”: “FAILURE”, “MESSAGE”: “The CRM key that you are using is for the older version of the API. Please generate the key for CRM API Version 2 and try again.”, “TOTAL_RECORDS”: 0, “RESPONSE”: [] }

Possible Causes

You are using the Version 1 API key in Version 2 API for integration. Please use the Version 2 API key or generate a new Version 2 Key and try again.

Advanced Troubleshooting

You observe that the API is giving proper JSON output, when you run it through your Browser on your Personal Computer, but is not working when the API Key is being used within the CRM Software that you are using. Then follow these steps (we are assuming that your server is a Linux machine, if it is a Windows Server, use equivalent commands):

From the command prompt of the Server do ping to mapi.indiamart.com to check, if IndiaMART’s API Server is reachable from your Server.

shrey_indiamart@shrey:~$ ping mapi.indiamart.com -n 

PING mapi.indiamart.com (34.102.235.255) 56(84) bytes of data.

64 bytes from 34.102.235.255: icmp_seq=1 ttl=112 time=23.9 ms

64 bytes from 34.102.235.255: icmp_seq=2 ttl=112 time=19.9 ms

64 bytes from 34.102.235.255: icmp_seq=3 ttl=112 time=18.7 ms

64 bytes from 34.102.235.255: icmp_seq=4 ttl=112 time=18.6 ms

64 bytes from 34.102.235.255: icmp_seq=5 ttl=112 time=21.0 ms

64 bytes from 34.102.235.255: icmp_seq=6 ttl=112 time=22.3 ms

64 bytes from 34.102.235.255: icmp_seq=7 ttl=112 time=19.6 ms

64 bytes from 34.102.235.255: icmp_seq=8 ttl=112 time=20.8 ms

64 bytes from 34.102.235.255: icmp_seq=9 ttl=112 time=20.4 ms

64 bytes from 34.102.235.255: icmp_seq=10 ttl=112 time=23.3 ms

64 bytes from 34.102.235.255: icmp_seq=11 ttl=112 time=21.6 ms

^C

--- mapi.indiamart.com ping statistics ---

11 packets transmitted, 11 received, 0% packet loss, time 10011ms

rtt min/avg/max/mdev = 18.613/20.910/23.856/1.648 ms

The above output indicates that the average ping time is 6.293 ms to IndiaMART’s Server.

Now, from the command prompt do a traceroute (windows: tracert) to IndiaMART’s Server:

shrey_indiamart@shrey:~$ traceroute mapi.indiamart.com

traceroute to mapi.indiamart.com (34.102.235.255), 30 hops max, 60 byte packets


 1  reliance.reliance (192.168.29.1)  2.799 ms  2.752 ms *

 2  10.28.232.1 (10.28.232.1)  17.872 ms  19.054 ms  19.037 ms

 3  172.16.23.1 (172.16.23.1)  19.037 ms 172.16.23.5 (172.16.23.5)19.017 ms 
    19.008 ms

 4  192.168.112.170 (192.168.112.170)  18.971 ms 192.168.112.168 (192.168.112.168)  18.977 ms  18.968 ms

 5  172.26.110.53 (172.26.110.53)  18.941 ms  18.928 ms  20.736 ms

 6  172.26.110.66 (172.26.110.66)  21.451 ms  10.908 ms  23.412 ms

 7  172.25.86.126 (172.25.86.126)  17.469 ms 172.25.86.124 (172.25.86.124) 
    24.295 ms 172.25.119.228 (172.25.119.228) 24.236 ms

 8  172.25.119.231 (172.25.119.231)  24.218 ms  24.198 ms  24.176 ms

 9  172.25.115.26 (172.25.115.26)  31.027 ms 172.25.115.24 (172.25.115.24)
    26.937 ms 172.26.14.75 (172.26.14.75)  32.794 ms

10  172.16.23.6 (172.16.23.6)  32.773 ms  33.802 ms 172.16.23.0 (172.16.23.0)
    32.727 ms

11  172.16.0.56 (172.16.0.56)  34.444 ms 172.16.0.36 (172.16.0.36) 
 32.734 ms 
    172.16.0.56 (172.16.0.56)  32.664 ms
12  209.85.245.111 (209.85.245.111)  22.300 ms 74.125.243.97 (74.125.243.97) 
    18.260 ms 142.251.66.175 (142.251.66.175)  39.802 ms

13  172.253.67.85 (172.253.67.85) 39.744 ms 255.235.102.34.bc.googleusercontent.com
    (34.102.235.255)  39.718 ms 64.233.174.151 (64.233.174.151)  39.760 ms

The above output indicates that the IndiaMART’s Server is reachable in 12 hops within 5 to 6 ms. It also helps in identifying that if any particular hop is taking remarkably high time.Now, let’s see how is the API call working from the Server using Linux curl command (Windows’ PowerShell provides a command similar to curl called Invoke-WebRequest):

shrey_indiamart@shrey:~$ curl -w "\n DNS_Resolution: %{time_namelookup}s\n 
TCP_Established:%{time_connect}s\n SSL_Handshake_Done: %{time_appconnect}s\n 
Time_PreTransfer: %{time_pretransfer}s\n
 Time_Redirect: %{time_redirect}s\n TTFB: 
%{time_starttransfer}s\n Time_Total: %{time_total}s\n" -o
/tmp/output.txt-s "https://mapi.indiamart.com/wservce/crm/
crmListing/v2?glusr_crm_key=MTYxNzg2NjY0Mi43MDI4IzE5MTY5MTI="

 DNS_Resolution: 0.032216s
 TCP_Established: 0.052672s
 SSL_Handshake_Done: 0.106323s
 Time_PreTransfer: 0.106524s
 Time_Redirect: 0.000000s
 TTFB: 0.711358s
 Time_Total: 0.711614s

The above output gives the breakup of each stage of connection to IndiaMART’s API call. Check what is taking time. Also, the output is saved in the file /tmp/output.txt (check the output using the command cat or more to see if you are getting proper JSON output).

Frequently Asked Questions(FAQs)

1. We want all Leads data since the onboarding/start of our service at IndiaMART for remarketing API

Generally, any outbound data sync API gives data from the day the API is integrated. But, IndiaMART API gives a facility to specify a date range of 7 days, and the old data for the last 365 days can be fetched. This is also documented in the API Integration documentation at point number 4 of the “Points to remember while using this API and output” section. The dataflow pipeline and the aggregated data structured for the API at the backend is architectured to fetch and store data for the CRM API only for the last 365 days. Older data is automatically removed from API’s pipeline, this is done for optimal performance.

2.Is there any way by which data prior to the last 365 days could be made available in the CRM API?

Sorry, this is not possible. Please see Q1.

3. We are getting the Leads data into our CRM quite late with hours of delay.

Check the Scheduler of your CRM Software in use. Ask your Software Technical Team or the CRM Vendor’s Technical Team or the Plugin Developer’s support Team (if you are using any plugin for the CRM being used) to check the scheduled interval of API requests. Also, refer to the “Suggested API Hit strategy” section of this document. You can also check the CRM logs available on Lead Manager, which will be helpful in identifying if there is a delay due to the current API hit strategy that you are using.

4. We wish for a Push API instead of the current Pull API, which should push the Leads data automatically to our CRM as it comes or better to say a webhook which we can provide and you update it.

A lot of IndiaMART Clients who have connected IndiaMART CRM API with their own in-house CRM Software are not hosted on Public Cloud i.e not on Public dedicated IP-address. They even switch off their CRM System during off-office hours. That’s why we provided an on demand / scheduled polling-based API, which is better for everyone. Also, it will be unmanageable for us to cater to different Webhooks having different preconditions.

Check the Scheduler of your CRM Software in use. Ask your Software Technical Team or the CRM Vendor’s Technical Team or the Plugin Developer’s support Team (if you are using any plugin for the CRM being used) to check the scheduled interval of API requests. Also, refer to the “Suggested API Hit strategy” section of this document. You can also check the CRM logs available on Lead Manager, which will be helpful in identifying if there is a delay due to the current API hit strategy that you are using.

5. We wish to get a large date range in one go to pull the Leads data, the current API has a restriction of 7 days window.

As the CRM API’s output is transmitted over HTTP in JSON format, a large data set will timeout due to longer transfer time. Generally, if you have scheduled the API polling at a 10-15 minutes interval from within your CRM Software, you just need delta data of the past 10-15 minutes.

If you are integrating for the first time and wish to synchronize past data, program your CRM to pull 7 days of data in a rolling window, starting from the date 365 days prior to the current date. For example, if you are integrating on 1st Jan 2022 then the 1st request for 1st Jan 2021 to 7th Jan 2021, then 8th Jan to 14th Jan, and so on. (For the Software, it’s very easy but if you are doing it manually, it’s tedious).

6. We are getting duplicate leads in CRM (overlapping date range as well as repeat contacts via enquiry / pns call). what to do in such cases.

This happens due to two reasons. One, if you are calling the API with overlapping date/time ranges, some records from the overlapping window will be duplicated. Two, if the same Buyer has sent multiple Enquiries including Calls, they all will come as separate records, but you may be considering them duplicates. Refer to point number 7 of the “Points to remember while using this API and output” section of this document.

7. We wish to stop the API CRM integration.

If you are using any third-party CRM Software, there must be an option to disable the API Key or Speak to the Customer Care of the Software you are using. If you are using it through any in-house Software, ask your Technical Team to remove the API Key. Once no hit comes for the particular API-Key on IndiMART’s Servers for 15 consecutive days, the Key will automatically expire.

8. Unable to connect my CRM Portal with Indiamart’s API.

Please refer to the “Advanced Troubleshooting” section of this document. That will give you clues as to where exactly the problem is.

9. We have already integrated our CRM, but now Leads are not reflecting in the CRM.

This will need to be first debugged by your Technical Team, in case of in-house CRM use, or the CRM plugin Vendor you have purchased, or the CRM Vendor’s Technical Team. They should check the API call response/output or any error message it throws. The error may not show up on the front end, but the Tech Team may be able to see the error on the Server’s error logs. You can also check the API Logs on Lead Manger to see if your CRM is sending the correct requests and leads are being returned or not or if it is returning any error. Also, the “Advanced Troubleshooting” section of this document can help your Tech Team to debug.

10. How do we integrate the IndiaMART CRM API with Google Sheets or Microsoft Excel (Integration with any other similar software)?

The Google Sheet, as well as Microsoft Excel, have in-built Programming / Scripting language Google Apps Script (JavaScript) and Visual Basic for Applications respectively. So, theoretically, scripts can be written within Google-Sheets and MS-Excel to poll the IndiaMART CRM-API and transform the JSON output into columns. It will also require programmatically calling the API with moving date-time ranges with scheduling. But, we haven’t tried it ourselves. You may depute expert Programmers to do the automation. As IndiaMART’s CRM API is provided in DIY (Do it Yourself) mode, IndiaMART’s Technical Team won’t do any hand-holding or provide any technical assistance for this too.

11. Some Leads are not getting into our CRM from IndiaMART LMS.

It may be due to incorrect scheduling of the API polling through your CRM software used. Refer to the “Suggested API Hit strategy” of this documentation. Or it may also be due to some filtration/deduplication logic implemented into your CRM Software. The CRM API logs available on the lead manager can be used to check the number of leads received and crosscheck it with the number of leads added in the CRM.

12. Which CRM Software we should purchase, which is best suited to connect with IndiaMART CRM API? Which external CRM Softwares are Compatible with integration?

There are several CRM software available in the market, which integrate IndiaMART’s CRM API. Some of them inherently have features to connect IndiaMART’s API, whereas some require a fourth party plugin for additional cost apart from the cost of the CRM that you are purchasing. We do not recommend any specific solution as a preference. Rather, we suggest using the Lead Manager of IndiaMART, without incurring any extra cost.

13. The “Generate Key” option is not showing for my Setting > Account Setting.

The “Generate Key” option is available to only Paying Clients of IndiaMART. If you are already a Paying Client, cross check if you have logged-in with a correct registered Primary Mobile Number associated with your Account.

14. Could data be made available in any other format apart from JSON format?

Sorry, we do not have any plans to customize the API output in any other format other than JSON. In fact JSON format is the most suitable format for API output consumption by any Software and automation.

15. We wish to take technical assistance from IndiaMART’s Technical Team, for CRM API Integration with our CRM Software.

The IndiaMART’s CRM API is provided in DIY (Do it Yourself) mode, thus IndiaMART’s Technical Team won’t do any hand holding. The detailed steps of integration are already mentioned in this document, which is easy to understand by your Technical Team or your CRM Vendor’s Technical Team or Technical Team of Plugin providers. This document also mentions different error messages by the API. There is an Advanced Troubleshooting section too, mentioning steps to debug. In case you still feel that support is needed, please send your issue with complete technical detail and output of the diagnostics done through IndiaMART’s Customer Care. Remember, we do not know the internal working of the 3rd Party CRM that you may be using.

16. We have integrated the API in our CRM, but nothing is coming.

Please follow the “Advanced Troubleshooting” detailed in this document.

17. Can you please provide the full name of the country instead of the country code in the field country_iso as my CRM is unable to identify it?

As there is no standard way to write a Country name. For example, India is written as “India” or “The Republic of India” or “Bharat”. Similarly, China is written as “China” or “The People’s Republic of China” and so on. It’s better to follow ISO country codes. ease follow the “Advanced Troubleshooting” detailed in this document.

The ISO country codes are internationally recognized codes that designate every country and most of the dependent areas as a two-letter combination; it is like an acronym that stands for a country.

These are based on the ISO 3166-1 alpha-2 standard – refer tohttps://www.nationsonline.org/oneworld/country_code_list.htm