Sulekha Leads Integration

3rd Party Leads Integration Updated Aug 04, 2026

Use this API to send leads from Sulekha directly into Abstract One CRM. When a user enquires about your project on Sulekha, Sulekha will call this endpoint to create the lead in your CRM with the correct project and campaign mapping.

This is a global API endpoint. Your CRM account is identified using the x-api-key header — no client-specific configuration is required in the URL itself.

Sharing with Sulekha

To integrate Sulekha with your Abstract One CRM, share the following with your Sulekha technical contact person:

This documentation page URL
API Key — from your CRM. See Generate API Key.
Project ID — for each project listed on Sulekha. See Get Project ID.
Campaign ID — for the campaign linked to that project. See Get Campaign ID.

Important: The campaignID must belong to the same project as the projectID you pass in the request. If you list multiple projects on Sulekha, provide a separate Project ID and Campaign ID pair for each project.

Endpoint

POST https://app.abstractone.in/api/sulekha-lead-create

Request headers

Include these headers in every API request:

Header	Value	Description
`x-api-key`	`your_api_key_here`	Your API key from CRM. See Generate API Key.
`Accept`	`application/json`	Expected response format
`Content-Type`	`application/json`	Request body format

Request body

Send lead data as a JSON object in the request body.

Required fields

Field	Type	Description
`name`	string	Lead full name
`mobile_number`	string	10-digit Indian mobile number (starts with 6–9). Country code and spaces are stripped automatically — only the last 10 digits are used.
`projectID`	string	Project ID from CRM (e.g. `AAP002`)
`campaignID`	string	Campaign ID from CRM (e.g. `AAC001`). Must belong to the selected project.
`notes`	string	Lead enquiry details or message from Sulekha (e.g. configuration preference, enquiry text)

Optional fields

Field	Type	Description
`email`	string	Lead email address
`alternate_number`	string	Alternate mobile number (10 digits, must differ from `mobile_number`)

Example request

curl --location 'https://app.abstractone.in/api/sulekha-lead-create' \
--header 'x-api-key: your_api_key_here' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{
  "name": "Rahul Sharma",
  "mobile_number": "9876543210",
  "alternate_number": "9123456780",
  "email": "rahul@example.com",
  "projectID": "AAP002",
  "campaignID": "AAC001",
  "notes": "Interested in 2BHK at Abstract Next, Kalyan"
}'

Success response

HTTP 200

{
  "status": true,
  "message": "Lead created successfully",
  "data": { }
}

The data object contains the created lead details from CRM.

Error responses

HTTP Status	Message	Cause
`401`	API Key missing	`x-api-key` header not provided
`401`	Invalid API credentials	API key is incorrect or inactive
`404`	Client not found	API key does not map to a valid CRM account
`422`	Project not found	`projectID` does not exist in CRM
`422`	Campaign not found	`campaignID` does not exist in CRM
`422`	Lead already exists	Duplicate mobile number for the same project (when duplicacy mode is set to ignore)
`500`	Error message	Unexpected server error during lead creation

Integration flow

A user submits an enquiry for your project on Sulekha.
Sulekha sends the lead data to this API endpoint.
Pass the correct projectID and campaignID for the project the user enquired about.
Include your x-api-key in the request headers.
Abstract One CRM creates the lead with source tagged as Sulekha and assigns it based on your pipeline rules.

Duplicate leads

Abstract One checks for existing leads with the same mobile number within the same project. Behaviour depends on your CRM Lead Duplicacy setting:

Ignore — duplicate leads are rejected with a 422 response.
Create — a new lead is created and marked as repeated.
Merge — a new lead is created and linked to the original parent lead.

Testing

Before going live, Sulekha or your team should send a test request with sample data and verify the lead appears in your CRM under the correct project and campaign with the Sulekha source.