Nextdoor Local Leads — phone-verified business leads in 60 seconds

$5 per 1,000 leads · half the price of competing scrapers · free trial included

Pull phone-verified local business leads from Nextdoor for any service category in any US metro. Auto-flags unclaimed Nextdoor pages with high recommendation counts — the perfect signal for cold outreach in lead-generation, agency, and GoHighLevel workflows.

What you get

Each row in the output dataset:

Field	Example
category	plumber
name	Anthony The Plumber
phoneFormatted	(314) 288-8712
phoneE164	+13142888712
fullAddress	5604 Walsh St, Saint Louis, MO 63109
recommendationCount	315
isUnclaimedLead	true
description	Plumbing service based in St. Louis, Missouri…
url	https://nextdoor.com/page/anthony-the-plumber-saint-louis-mo

Import directly into GoHighLevel, HubSpot, Apollo, Instantly, Smartlead, Lemlist, or any CRM.

How to use it (2 minutes the first time)

You provide your own Nextdoor session — that's the only thing that makes this ToS-defensible. There's a 1-click Chrome extension that does this for you:

Option A — Chrome extension (recommended for non-technical users)

1. Install Apily Session Capture (free): [link to Chrome Web Store — coming soon] Until the Web Store listing is live, install as unpacked extension from the apily/apily monorepo — see extensions/nextdoor-cookie-capture/README.md
2. Log into https://nextdoor.com in any tab
3. Click the extension icon → Copy session to clipboard
4. Come back to this actor, click Start, paste the clipboard into the Nextdoor Cookie header field — paste the csrftoken field separately from the JSON
5. Pick your categories (default: plumber, electrician, roofer, landscaper, dentist)
6. Click Start → leads appear in the Dataset tab in ~3 minutes

Option B — Manual (developers)

1. Open https://nextdoor.com in a logged-in Chrome tab
2. DevTools (Cmd+Opt+I) → Network tab → click any request to nextdoor.com
3. Right column → Request Headers → find the Cookie: line → copy the entire value
4. Paste into the Nextdoor Cookie header field
5. From the same Cookies list, find csrftoken → copy just the value → paste into csrftoken field
6. Click Start

A captured session typically lasts ~30 days before Nextdoor rotates it.

Pricing

This actor uses Apify's Pay per result model:

• Free trial: first run free, up to 25 results
• After free trial: $0.005 per dataset item = $5 per 1,000 leads

Compare: competing Nextdoor scrapers charge $10+ per 1,000 leads. You're paying half.

For high-volume users (50,000+ leads/month), our direct API at apily.dev/nextdoor offers a fixed monthly subscription at ~$0.17 per 1,000 leads. Subscribe there to skip Apify's per-result pricing entirely.

How to get access — no separate API key needed

Any Apify account can run this actor. Apify handles authentication + billing:

• Free Apify account → free trial run
• After the free trial, Apify charges your credit card per result
• You'll see line items on your Apify invoice clearly labeled "Nextdoor Local Leads"

You only pay for results you actually get. If the actor returns 0 leads (your session expired, no businesses matched your filter), you pay nothing.

For the direct Apily API (instead of going through Apify), get a key at https://apily.dev/nextdoor — email arrives within 24 hours with a Stripe Checkout link.

Inputs

Field	Description	Default
categories	Service categories	["plumber","electrician","roofer","landscaper","dentist"]
metroSlug	Nextdoor city slug	saint-louis--mo
enrich	Add phone/hours/claim status per business	true
onlyUnclaimed	Filter to businesses with no admin claim	true
minRecommendations	Drop pages below this many recommendations	25
maxResultsPerCategory	Cap per category to control cost	50
nextdoorCookieHeader	Your Nextdoor Cookie header	required
nextdoorCsrfToken	Your csrftoken value	required

How it works

The actor runs Nextdoor's own GraphQL operations as if you were browsing the site — using your session. Two calls per result: one to search for businesses in your category, one to fetch the per-business detail (phone, hours, claim status). Results are filtered by your onlyUnclaimed + minRecommendations rules, then deduped and pushed to the dataset.

We never store your session. It's used only for this run.

Limits and caveats

• One Nextdoor metro per run. Set metroSlug to target a specific market.
• Session expiry. Nextdoor sessions last ~30 days.
• CAPTCHA challenges are possible at high sustained request rates (50+ req/min from one session). Built-in 200–600ms jitter stays under this.
• Persisted query hash rotation. Nextdoor rotates GraphQL hashes every few weeks. If you see PERSISTED_QUERY_NOT_FOUND, open an issue — we patch within 24 hours.

Use cases

• GoHighLevel agencies — Find unclaimed pages with 100+ recommendations in your metro. Pitch "we'll manage your Nextdoor + Google" to highly-qualified prospects.
• Local marketing consultants — Map every category in a metro. Sell SEO + reputation to businesses with high real-world traction but no online presence.
• B2B SDRs at home-services SaaS (Jobber, Housecall Pro, ServiceTitan) — TAM mapping by territory.
• Independent contractors — Audit your own market: competition, rec count, claim status.

Privacy + ToS

This actor uses your own Nextdoor session, not ours. Each customer hits Nextdoor as themselves — the only ToS-defensible model.

We do not store, log, or transmit your session anywhere except to Nextdoor itself, scoped to the duration of one run.

The data exposed (business name, phone, address, recommendations) is already publicly visible to any logged-in Nextdoor user in the relevant metro. We don't expose private member data or anything behind a paywall.

Support

• Open an issue on the actor page
• Email: hi@apily.dev
• Direct subscription: apily.dev/nextdoor

Changelog

• 0.0.2 (2026-05-29) — initial public release
• 0.0.1 — internal development build