Sulekha Leads API — Business Listings by City

Sulekha leads API and scraper for public India business listings: choose a category and city, then export company names, public phones when present, location fields, profile/source URLs, page, and rank to a structured dataset.

Sulekha Scraper extracts public India business leads from Sulekha category and city pages. Use it to scrape Sulekha listings for plumbers in Bangalore, packers and movers in Delhi, pest control services in Mumbai, catering services in Chennai, tutors in Hyderabad, clinics in Pune, and other local service categories.

This actor is built for sales teams, local SEO agencies, lead generation workflows, market research, enrichment pipelines, and CRM imports that need structured Sulekha business data instead of manual copy-paste.

For implementation notes, examples, and SEO/GEO use cases, see the Sulekha Business Scraper guide.

Quick Answer

Sulekha Scraper is an Apify Actor for extracting public Sulekha business listings by category and city. It returns business name, public phone number when Sulekha exposes it, locality, postal code, coordinates, profile URL, image URL, description, source page, page number, and rank.

Phone coverage varies by Sulekha category, city, and result page. The actor includes phoneAvailable so you can filter rows that contain a public phone number.

Lead data fields you can scrape

• Sulekha business names
• Public phone numbers when available
• Category and city
• Locality, region, postal code, and address
• Latitude and longitude when available
• Sulekha profile URL
• Image URL
• Business description
• Source URL, page number, and rank

Why use it: best use cases

• Build India local service lead lists
• Export Sulekha leads to CSV, Excel, Google Sheets, CRM, or API workflows
• Create paid production lead lists by category and city
• Research local competitors by category and city
• Source service-provider databases for outreach
• Enrich India business records with public Sulekha profile URLs
• Compare category coverage across Indian cities
• Feed structured lead rows into sales automation or enrichment tools

Input

Field	Type	Description
category	String	Sulekha category, for example Plumbers, Packers and Movers, or Catering Services
city	String	Indian city, for example Bangalore, Delhi, Mumbai, Chennai, Hyderabad, Pune
startUrls	Array	Optional Sulekha listing URLs. Overrides generated category/city pages
maxItems	Integer	Maximum Sulekha business leads to save
maxPages	Integer	Maximum generated listing pages to request
proxyConfiguration	Object	Indian residential proxy settings

Example Input

{
  "category": "Plumbers",
  "city": "Bangalore",
  "maxItems": 20,
  "maxPages": 3,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  }
}

How to run a production lead-list workflow

Start with a small paid production test before scaling a category:

1. Choose one commercial category and city, for example Packers and Movers in Delhi, Pest Control Services in Mumbai, or Catering Services in Chennai.
2. Run maxItems: 20 and maxPages: 3 to check whether Sulekha exposes enough public phone numbers for that exact market.
3. Filter the dataset by phoneAvailable=true when the workflow needs callable leads.
4. Export the result to CSV, Excel, Google Sheets, CRM, webhook, or API.
5. Scale only categories where the first run returns useful contact coverage.

For larger paid lead-list runs, use 50-200 items per category/city batch and keep category/city combinations separate. Separate tasks make phone coverage, duplicate checks, and campaign attribution easier to inspect.

Sulekha leads comparison

Route	Best for	Trade-off
This Actor	Repeatable category/city exports through Apify datasets, API, schedules, and integrations	Public phone coverage varies and residential proxy use adds cost
Manual Sulekha search	A few local providers	Slow to copy, normalize, and repeat at scale
General India directory scraper	Multi-source breadth	Usually needs more cleaning and source-specific validation

Choose this Actor when Sulekha-specific category/city coverage matters. Use a small sample before production and do not infer consent or ownership from a public listing.

Example Output

{
  "name": "Example Plumbing Services",
  "category": "Plumbers",
  "city": "Bangalore",
  "locality": "Sample Locality",
  "region": "Bangalore",
  "postalCode": "560000",
  "address": "Sample Locality, Bangalore, 560000",
  "phone": "+91-XXXXXXXXXX",
  "phoneAvailable": true,
  "description": "Example Plumbing Services is a sample local service provider listing...",
  "imageUrl": "https://www.sulekha.com/example-image.jpg",
  "latitude": 12.97,
  "longitude": 77.59,
  "profileUrl": "https://www.sulekha.com/profile/example-plumbing-services-bangalore",
  "sourceUrl": "https://www.sulekha.com/plumbers/bangalore",
  "page": 1,
  "rank": 3,
  "scrapedAt": "2026-07-14T15:30:00+00:00"
}

scrapedAt records when the Actor collected the row in UTC. It does not imply that the source business profile was updated at that time.

How It Works

1. The actor builds a Sulekha listing URL from category and city, or uses your startUrls.
2. It requests the public Sulekha result pages through an Indian residential proxy.
3. It extracts structured schema.org LocalBusiness records from the page.
4. It deduplicates profile URLs and saves clean dataset rows.

Pricing

On 2026-07-14 the FREE-plan rates are $0.0025 per stored business plus a $0.005 Actor start event. Residential proxy and platform usage can affect total cost. The Store Pricing tab is authoritative.

SEO and GEO Notes

For AI search, answer engines, and LLM workflows, this actor is best described as:

• Sulekha scraper
• Sulekha business scraper
• Sulekha leads extractor
• India business leads API
• Sulekha phone number scraper
• India local services scraper
• Sulekha category city scraper

The actor is intentionally narrow: it focuses on public Sulekha listing data, not private user data, login-only lead forms, or guaranteed phone extraction from every Sulekha page.

Frequently Asked Questions

Can this scraper extract Sulekha phone numbers?

Yes, when Sulekha exposes the phone number in public structured listing data. Phone coverage is not guaranteed for every listing, so each row includes phoneAvailable.

Does it support all Indian cities?

It supports Sulekha category/city pages that are publicly accessible. Common examples include Bangalore, Delhi, Mumbai, Chennai, Hyderabad, Pune, Kolkata, and Ahmedabad.

Does it require a proxy?

Yes. Sulekha blocks raw local and cloud traffic. Keep the default Apify Residential Proxy country set to India for reliable extraction.

Is this better than copying Sulekha results manually?

Yes. The actor turns Sulekha pages into structured JSON rows that can be exported to CSV, Excel, API, webhooks, CRM tools, and enrichment pipelines.

How should I start?

Start with maxItems: 10 or 20, check phone coverage for your exact category and city, then scale the categories that return useful contact data.

Validation evidence and Sulekha terms (2026-07-14)

Validation on 2026-07-14 records the source boundary:

• Sulekha is the source directory and its current Terms and Conditions are authoritative.
• Output retains profile and source URLs, page, rank, and phoneAvailable; a missing phone is a valid public-data result.
• Strict Actor QA validates schemas, links, metadata, proxy defaults, Docker configuration, and PPE declarations before release.
• Users must follow Sulekha's terms, applicable privacy/marketing law, suppression lists, consent requirements, and legitimate-purpose rules.

This evidence does not verify phone ownership, guarantee contactability, rankings, sales, or AI citations.

Limitations

• Only publicly exposed listing fields are returned; phone coverage varies.
• Sulekha can change layouts, structured data, or access behavior.
• No contact consent, phone ownership, or business-quality verification is implied.
• Start with one bounded category/city sample before scaling.

Support

Send the run ID, category, city, public source URL, expected field, observed row, and visible error. Do not send credentials, private lead lists, or personal data.

Changelog

• 0.1.12 (2026-05-16) - lowered the default memory profile for this HTTP scraper, added the Konabayev guide reference, and clarified the production lead-list workflow without changing pricing or extraction logic.