Nextdoor Originals APInextdoororiginals.co ↗
Extract structured event data from nextdoororiginals.co pages — title, date, time, venue, location, description, and image URL via one endpoint.
What is the Nextdoor Originals API?
The Nextdoor Originals API provides access to event details from nextdoororiginals.co through a single get_event endpoint that returns up to 8 structured fields per event page, including title, start date, start and end times, venue name, street address, full description text, and a primary image URL. Pass any event page URL and receive normalized, structured data ready to use in calendars, event aggregators, or marketing tools.
curl -X GET 'https://api.parse.bot/scraper/e721c6b4-9417-452e-a246-f4ca66367dd2/get_event?url=https%3A%2F%2Fnextdoororiginals.co%2Fpages%2Fparty-1' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve details for a single event from its page URL. Extracts structured data including title, date, time, venue, location, description, and a primary image. Fields that are not present on the page return null. Venue and location are parsed from the event description text when structured patterns are found (e.g. 'at <Venue> in <Location>').
| Param | Type | Description |
|---|---|---|
| urlrequired | string | Full URL of the event page on nextdoororiginals.co (e.g. https://nextdoororiginals.co/pages/party-1). |
{
"type": "object",
"fields": {
"title": "string — event title",
"venue": "string or null — venue/building name extracted from description",
"end_time": "string or null — event end time if mentioned",
"location": "string or null — street address or city/state extracted from description",
"image_url": "string or null — URL of the primary event image",
"start_date": "string or null — event date as displayed on the page",
"start_time": "string or null — event start time if mentioned",
"description": "string — full event description text"
},
"sample": {
"data": {
"title": "FORGET THE NIGHT, REMEMBER THE NAME",
"venue": "STUDIO KILLA",
"end_time": null,
"location": "MARRICKVILLE, NSW, AUSTRALIA",
"image_url": "https://nextdoororiginals.co/cdn/shop/files/FORGET_THE_NIGHT_REMEBER_THE_NAME_EVENT_PAGE.png?v=1760071040&width=4000",
"start_date": "DECEMBER 16TH, 2023",
"start_time": null,
"description": "NEXTDOOR HAD THEIR FIRST EVENT AT STUDIO KILLA IN MARRICKVILLE, NSW, AUSTRALIA. THE EVENT WAS SUPPLIED WITH FREE ALCOHOL BY FIREBALL & PALS, PHOTOGRAPHED BY LIFE WITHOUT ANDY AND HEADLINED BY INTERNATIONAL HEADLINE DJ'S \"YOLANDA BE COOL\""
},
"status": "success"
}
}About the Nextdoor Originals API
What the API Returns
The get_event endpoint accepts a single required parameter — url — which must be a full URL to an event page on nextdoororiginals.co (for example, https://nextdoororiginals.co/pages/party-1). The response contains up to 8 fields: title, start_date, start_time, end_time, venue, location, description, and image_url. Fields that are not present on the source event page are returned as null rather than omitted, so response shape is consistent across all calls.
Field Details and Parsing Behavior
The venue and location fields are parsed from the event description text rather than from dedicated metadata, which means their presence depends on how the event organizer structured the page copy. start_date is returned as displayed on the page (not normalized to ISO 8601), and start_time / end_time are returned as plain strings when the page mentions them. image_url points to the primary event image when one is present.
Coverage and Scope
This API covers public event pages on nextdoororiginals.co. It does not require authentication. Only one event record is returned per call — there is no batch or listing endpoint. If the target page has no distinct date, venue, or time information, those fields will be null in the response.
The Nextdoor Originals API is a managed, monitored endpoint for nextdoororiginals.co — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when nextdoororiginals.co changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official nextdoororiginals.co API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Populate a community event calendar using
start_date,start_time, andvenuefromget_event. - Aggregate Nextdoor Originals party listings into a local events newsletter with titles and descriptions.
- Display event cards in a web app by pulling
title,image_url, andlocationfor each event page. - Monitor event details for changes in date, time, or venue over time by periodically calling
get_event. - Extract event descriptions to feed into a content pipeline or summarization workflow.
- Build a structured dataset of Nextdoor Originals events for local nightlife or entertainment research.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Nextdoor Originals have an official developer API?+
What does the `get_event` endpoint return when venue or location data is missing from the page?+
venue and location return null when they cannot be identified in the event description text. The title and description fields are always populated if the page exists; all other fields return null when not present.Can the API return a list of all upcoming events from the site, rather than one event at a time?+
get_event endpoint, one URL per call. You can fork the API on Parse and revise it to add a listing endpoint that returns multiple upcoming events.Are dates and times returned in a standardized format like ISO 8601?+
start_date, start_time, and end_time are returned as plain strings exactly as they appear on the event page — no normalization or timezone conversion is applied. If your application requires a specific format, you will need to parse and convert these values after retrieval.