Our API suite gives developers a way to programmatically integrate with the LeadSquared CRM. Once integrated, you can create, update, delete and retrieve information on leads, activities, tasks, emails and lots more.

Our APIs, based on the REST framework, are language agnostic. You can call them using any programming language that allows you to make HTTP requests like Ruby, PHP, Java, etc.

Yes, each API in our reference guide has a Try It button you can use for testing before you write any code.

Firstly, you must be a LeadSquared user. If you aren’t already a user, you can view our subscription plans here. Once you’ve registered, a good place to start would be the API reference guide on this site.

Yes, you can get a free trial for a 15 day period. For more information, visit our website.

Once you’ve signed up with LeadSquared you’ll get an Access Key and a Secret Key. These are confidential keys that authorize API calls for each user. You’ll have to pass them in the API URL of all your requests. You’ll get a 401 “Unauthorized” response for requests with missing or invalid API keys.
Be sure to keep your keys secret and don’t share them with anyone or expose them in any public areas or client-side code.

To get your API keys, go to  My Account>Settings>API and Webhooks. Your API host will also be visible on the same page.
For more information, see How Do I Obtain My Access Keys.

Yes, rate limits are determined by your LeadSquared plan. If you exceed that limit all your API requests will result in errors. See the Rate Limits section of the API Overview for more information.

All API responses will be in the JavaScript Object Notation (JSON) format.

Whether the page visit and lead source information is captured depends on the API you use to integrate your website form with LeadSquared. If you used the Create a Lead API, this information won’t be tracked.

To capture page visit and lead source info., use the Capture Leads or Convert a Visitor to Lead APIs and ensure that the ‘MXCProspectId” (used to track website visitors) is being passed to the API.

It’s not necessary, but we highly recommend logging the API responses at the user’s end. This is especially helpful when an API call fails with exceptions. The response code tells the user exactly what went wrong like if the authentication failed, there was a missing parameter, etc. It becomes easy for users to then figure out what went wrong by themselves.