Nextdoor API
Agent-ready OpenAPI document · curated by JenticMarketingAdvertisingoauth2, bearer29 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage Nextdoor ad campaigns with targeting, creatives, and reporting, publish and edit neighborhood posts, and search local content by location across 27 endpoints.
Use for: I need to create a local ad campaign on Nextdoor, Target Nextdoor ads by zip code and age range, Upload a video creative for my Nextdoor ad, List all ad groups in a campaign
Not supported: Does not handle direct-to-consumer e-commerce transactions, global social media distribution beyond local neighborhoods, or professional B2B networking - use for hyperlocal community advertising and neighborhood content distribution only.
Jentic publishes the only available OpenAPI specification for Nextdoor API, keeping it validated and agent-ready. The Nextdoor API provides access to advertising campaign management, content publishing on local neighborhoods, and local content discovery across posts, events, businesses, and marketplace items. The Advertising API covers advertiser accounts, campaign lifecycle management, ad groups with geographic and demographic targeting, creative management with media uploads, custom audience creation, and campaign reporting. The Content Publishing API enables third-party apps to post, edit, and comment on Nextdoor on behalf of users. The Content Display API provides location-based search across posts, events, businesses, marketplace listings, trending content, and public agency feeds.
Install Jentic One Beta
Connect the Nextdoor API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nextdoor API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnextdoor.com%2Fnextdoor" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnextdoor.com%2Fnextdoor" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Nextdoor API.
Create and manage advertising campaigns with budget control, scheduling, and status transitions
Configure ad groups with multi-faceted targeting including zip codes, cities, states, radius-based geofencing, demographics, devices, and custom interests
Design and deploy ad creatives with headlines, body copy, call-to-action buttons, images, videos, and landing page URLs
Build custom audiences and apply them to ad group targeting for retargeting and lookalike expansion
Generate campaign reports by advertiser, date range, and report type, or schedule recurring automated reports
Publish, edit, and delete posts on Nextdoor neighborhoods with text, media attachments, and link previews
Search location-based content including posts, events, businesses, marketplace items, and trending topics by city and state
Use Cases
Patterns agents use Nextdoor API for, with concrete tasks.
★ Hyperlocal Advertising Campaigns
Launch neighborhood-level advertising campaigns targeting specific zip codes, cities, or radii around business locations. Create an advertiser account via POST /advertiser/create, define a campaign with objective and budget via POST /campaign/create, then configure ad groups with POST /adgroup/create specifying zip-code-level targeting, age ranges, interests, and device types. Upload creative assets (images, videos, logos) with the /media endpoints, attach them to ad groups via POST /creative/create, and monitor campaign performance with POST /reporting/create. Integration time for direct Nextdoor ad management is 2-3 days for auth, campaign setup, and reporting pipelines. Through Jentic: under 1 hour.
Create an advertiser with POST /advertiser/create, create a campaign with budget $500 for the next 30 days via POST /campaign/create, create an ad group targeting zip codes 94102, 94103 with age range 25-45 via POST /adgroup/create, and verify the campaign is active
Local Business Content Distribution
Automate content publishing to Nextdoor neighborhoods for local businesses, community organizations, or government agencies. Authenticate via OAuth, retrieve user profile and neighborhood access with GET /me and GET /me/profiles, then publish posts with text, images, and links via POST /post/create. Edit existing posts with POST /post/edit, respond to neighbors with POST /comment/create, and remove outdated content with POST /post/delete. This API is suitable for businesses with physical locations that want to share updates, promotions, or event announcements directly to the neighborhoods they serve.
Use GET /me/profiles to retrieve accessible neighborhoods, then POST /post/create with body text announcing a local event and a link, and verify the post was created successfully
Local Content Discovery and Monitoring
Search and retrieve Nextdoor content for competitive intelligence, community sentiment analysis, or local market research. Query posts by keyword and location with GET /search/posts, discover local events with GET /search/events, find businesses near a lat/lng coordinate with GET /search/businesses, and browse marketplace listings with GET /search/marketplace. Retrieve trending posts by city or state with GET /trending/posts, or monitor public agency feeds with GET /agency/feed. All search endpoints accept latitude/longitude or city/state parameters for geographic filtering, making it possible to track conversations, sentiment, and activity in specific neighborhoods or metropolitan areas.
Use GET /search/posts with query='community garden' and lat/lng for a specific neighborhood to find relevant discussions, then GET /trending/posts with city='Seattle' to see trending local content
Automated Campaign Reporting and Optimization
Generate ad performance reports on demand or on a recurring schedule to track impression volume, click-through rates, conversions, and cost-per-action across Nextdoor campaigns. POST /reporting/create with advertiser_id, report_type, and date range for one-off reports, or POST /reporting/schedule with a cron-style schedule for recurring delivery. Integrate these reports into broader marketing dashboards or feed them to an optimization agent that adjusts bids, pauses underperforming ad groups, or reallocates budget across campaigns. Combined with POST /campaign/status/update and POST /adgroup/update, this enables closed-loop campaign management.
POST /reporting/create with advertiser_id and report_type='campaign_performance' for the last 7 days, retrieve the results, then POST /campaign/status/update to pause campaigns with CTR below 0.5 percent
AI Agent for Nextdoor Ad and Content Management
Let an AI agent handle common Nextdoor marketing tasks - launching a hyperlocal ad campaign, posting an announcement to neighborhoods, generating a weekly performance report, or searching for trending topics in a target market. Through Jentic, the agent searches by intent like 'create a nextdoor ad campaign' or 'post to nextdoor neighborhood', loads only the relevant endpoints and schemas, and executes with the OAuth token or bearer JWT securely isolated in your Jentic One instance. The agent never sees the raw credential, and teams avoid the 2-3 day integration lift required for direct Nextdoor API usage.
Use the Jentic search query 'create a nextdoor ad campaign' to find POST /campaign/create, load its schema, and execute with advertiser_id, campaign name, objective='awareness', and budget=$300
Key Endpoints
29 endpoints — jentic publishes the only available openapi specification for nextdoor api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/campaign/create
Create an advertising campaign with objectives, budget, and schedule
POST
/adgroup/create
Create an ad group with targeting and bid configuration
POST
/creative/create
Create an ad creative with headline, body, CTA, and media
POST
/reporting/create
Generate a campaign performance report for a date range
POST
/post/create
Publish a post to Nextdoor neighborhoods
GET
/search/posts
Search posts by keyword and location
GET
/trending/posts
Retrieve trending posts by city or state
POST
/audience/create
Build a custom audience for ad targeting
POST
/campaign/create
Create an advertising campaign with objectives, budget, and schedule
POST
/adgroup/create
Create an ad group with targeting and bid configuration
POST
/creative/create
Create an ad creative with headline, body, CTA, and media
POST
/reporting/create
Generate a campaign performance report for a date range
POST
/post/create
Publish a post to Nextdoor neighborhoods
GET
/search/posts
Search posts by keyword and location
GET
/trending/posts
Retrieve trending posts by city or state
POST
/audience/create
Build a custom audience for ad targeting
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Nextdoor API by hand means running the OAuth authorization-code flow for content and handling a separate bearer token for advertising, then adding the right Authorization header to campaign, ad group, creative, and post calls against ads.nextdoor.com. Through Jentic you install once, import the Nextdoor API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
The advertising and content operations use action paths like /campaign/create and /post/create with their targets in the request body rather than a resource id in the path, so scope your agent to the operations it needs, such as creating posts, while leaving campaign or audience creation out of the allowed set unless you add them.
Credential isolation
Your Nextdoor OAuth credentials and advertising bearer token are stored once, encrypted, by your own Jentic One instance and added as the Authorization header at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Nextdoor ad campaign' or 'post to a neighborhood' and Jentic returns the matching operation with its input schema and targeting options so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Nextdoor API through Jentic.
Why is there no official OpenAPI spec for Nextdoor API?
Nextdoor does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nextdoor API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Nextdoor API use?
The Nextdoor API supports OAuth 2.0 authorization code flow for user-authorized actions like posting content, and bearer JWT tokens for advertising operations. Through Jentic, credentials are stored encrypted in your Jentic One instance and injected at execution time, so tokens never enter the agent's context.
Can I target Nextdoor ads by zip code through the API?
Yes. The targeting configuration in POST /adgroup/create includes geo.zip_codes, geo.cities, geo.states, and geo.radius_miles for location-based targeting. You can also filter by demographics (age, gender), devices (desktop, mobile, tablet), and custom interests.
What are the rate limits for the Nextdoor API?
The Nextdoor API rate limits are not documented in the OpenAPI spec. Refer to the Nextdoor developer documentation at https://developer.nextdoor.com for current limits, which vary by endpoint category (advertising, content publishing, content display). Implement exponential backoff for 429 responses.
How do I create a Nextdoor ad campaign through Jentic?
Search Jentic for 'create a nextdoor ad campaign' to find POST /campaign/create. Load the schema, then execute with advertiser_id (from POST /advertiser/create), campaign name, objective (awareness, consideration, conversion), budget, start_time, and end_time. Jentic injects the OAuth or bearer token automatically.
Is the Nextdoor API free?
Nextdoor provides API access for approved partners and advertisers. Advertising API access typically requires a business relationship or minimum ad spend commitment. Content Publishing and Content Display APIs may be available to verified local businesses and organizations. Contact Nextdoor developer support for access approval.
Can I search for local events with the Nextdoor API?
Yes. Use GET /search/events with query text and lat/lng coordinates to find local events posted on Nextdoor near a specific location. This is part of the Content Display API and does not require user authentication if the events are publicly accessible.
Can I limit what my agent is allowed to do with the Nextdoor API?
Yes. Because you run Jentic One yourself, your own rules decide which Nextdoor operations and credentials the agent may use, and only the operations you allow can be called. The Nextdoor operations are action paths like /post/create, /comment/create, /campaign/create, /adgroup/create, and /audience/create, so you can allow an agent to publish neighborhood posts while leaving campaign, ad group, and audience creation out of its allowed set. Add the advertising operations only when a given agent actually needs to manage ads and reporting.
GET STARTED