Support for building on Neighbourly.io.
Everything you need to integrate the Neighbourly.io API with confidence — authentication, rate limits, endpoints, errors and webhooks — plus a direct line to our engineers when you're stuck.
Help with developers.
Neighbourly.io is a single REST API across ten data layers, built for teams that want property and location intelligence without stitching sources together. Most integration questions have a quick answer, and the ones that don't go straight to the engineers who built the platform.
Start with the topics below, check the common questions, and reach out any time — we'd rather unblock you fast than have you fighting an auth header at midnight.
Topics in this area.
Start here — most questions map to one of these.
Errors & debugging
Reading status codes and error payloads, handling empty results at a coordinate, and the fastest way to share a failing request with us.
Sandbox & going live
Testing against representative data before launch, and the checklist we run through with teams moving an integration into production.
What most people come here to do.
- Request API access and credentials
- Raise your rate limit or monthly volume
- Report an endpoint returning unexpected data
- Get help reproducing a failing request
- Ask about SDKs, webhooks or event delivery
How do I get access to the Neighbourly.io API?
Tell us what you're building through the contact form and we'll set you up with credentials and the right plan for your usage. Access is usually turned around within one business day.
How does authentication work?
Every request is authenticated with an API key tied to your plan and environment. Keys can be rotated at any time, and separate keys keep your testing and production traffic isolated.
What are the API rate limits?
Rate limits and monthly volumes depend on your plan. Every plan includes generous limits, and enterprise agreements can be tailored to your expected production load — talk to us before launch and we'll size it with you.
What format do responses come back in?
Responses are JSON, with data resolved to a coordinate and its place in the location graph so layers line up cleanly. Empty results at a coordinate are returned explicitly rather than as an error.
Do you support webhooks or change feeds?
Yes, on plans that include event delivery — so you can react to changes instead of polling. Ask us and we'll confirm what's available for your plan and use case.
Do you offer support SLAs for developers?
Response-time commitments are available on paid and enterprise plans. Tell us the level of coverage your team needs and we'll put the right SLA in place.
Other areas we help with.
Still need a hand?
Tell us what you're working on and we'll point you to the right product, plan or person.