Public plans only
The feed covers dated public activities. Private posts, member identities, home locations and attendance data stay outside it.
NAYBORLEE FOR DEVELOPERS
Local plans.
More possibilities.
Bring useful things happening nearby into the places people already look. One county at a time.
Apply for API access →Explore the endpoints ↓01 / PUBLIC READ ENDPOINT
A little local context,
ready to use.
Retrieve up to 30 published happenings for a five-digit US county FIPS code. Results include source attribution and sponsored disclosure when applicable.
Open the example feed ↗NO TOKEN REQUIRED
GET /api/happenings?county=13121What comes back
- The plan
- Title, summary, start and end times
- The place
- County code and broad location
- The source
- Source site, public URL and sponsorship fields
Available listings vary by county. An empty feed is a valid response.
02 / APPROVED SOURCES
Share the plans
you bring to life.
Submit dated public activities from your organization. New submissions and updates go through review before publication.
SubmitReviewPublish
SOURCE CREDENTIALS REQUIRED
POST /api/happenings
Authorization: Bearer <source-token>
X-Nayborlee-Source: <approved-site-slug>Include with each activity
A unique source event ID, county FIPS, title, summary, ISO 8601 start time, location label and HTTPS event URL.
202 · pendingAccepted for review. Publication follows approval.
Tokens are issued individually after review. Self-serve key issuance is not available yet.
BUILT AROUND TRUST
Useful information. Thoughtful boundaries.
Clear attribution
Keep the source with the activity. Sponsored submissions require separate authorization and a visible label.
A considered start
Expect source review, usage limits and a published API agreement before production access.
LET’S BUILD SOMETHING LOCAL
A good place to start.
Tell us about your public activity source, service area and integration plan. We’ll review it before issuing credentials.