Addresses, boundaries, neighbourhoods, permits, demographics, environmental context, and energy ratings — all keyed to the same address layer, all available from api.neighbourly.io/v1/. Built specifically for Canadian real estate.
Every Neighbourly data layer is keyed to the same validated address_id. Validate once, enrich with anything.
Validate, normalize, and geocode any Canadian address string. Typeahead autocomplete via Meilisearch. Viewport search via Elasticsearch geo_shape. ~100 street-type synonyms. SRID 4326 coordinates.
Address API →Six-level geographic hierarchy — Country → Province → County → Upper-Tier → Lower-Tier → Neighbourhood. MultiPolygon boundaries in GeoJSON, centroids, bounding boxes, and slug-based lookups.
Geography layer →Curated neighbourhood profiles with names, descriptions, boundary polygons, and character scores. Used by listing platforms to surface neighbourhood context on property pages.
Neighbourhood API →Municipal building permit records normalized to a consistent taxonomy. Query by address, city, date range, permit type, and status. Toronto, Vancouver, Calgary, Ottawa and more.
Permits API →Census-derived demographic profiles by FSA and neighbourhood — population, age distribution, household income, tenure, language, education, and commute data.
Demographics API →Environmental context for any property — flood risk zone, proximity to protected areas, air quality index, noise exposure estimates, and green space coverage within radius bands.
Environment layer →EnerGuide ratings, annual energy consumption, GHG emissions, heating fuel type, and efficiency scores — the most differentiated Neighbourly data layer, now available via API.
Energy API →Points of interest within configurable radius — transit, schools, parks, retail, healthcare, and more. Walk score proxies, transit frequency, and school catchment data.
POI layer →The address layer is the entry point. Everything else is a follow-up call keyed to the same address_id.
Generate a Bearer token or API key from your dashboard. Scoped access per environment — dev and prod keys are separate and individually revocable.
POST any Canadian address string to /v1/address. Receive a validated, normalized record with a persistent address_id.
Every address response includes _links to every data layer. Follow what your product needs — permits, demographics, energy, environment.
Store the address_id alongside your property records. Future calls to any layer skip address validation entirely — one ID, all layers, forever.
# 1. Validate the address GET /v1/address?q="88 Scott St Toronto" → { address_id: 9312, _links: { ... } } # 2. Pull permits GET /v1/permits?address_id=9312 # 3. Pull demographics for the FSA GET /v1/demographics/find?fsa="M5E" # 4. Pull neighbourhood context GET /v1/neighbourhood_by_slug?slug="st-lawrence" # 5. Pull energy data GET /v1/energy?address_id=9312 # 6. Pull environment GET /v1/environment?address_id=9312 → All responses keyed to address_id 9312
When a new listing enters your system, validate the address and attach permits, neighbourhood context, demographics, and energy data in a single async job. Surface it all on the listing page without building a data pipeline.
Add a Neighbourly data panel to every property in your CRM. Agents see permit history, neighbourhood scores, and energy ratings before they walk into a showing — without leaving your platform.
Instead of assembling data from five different sources with five different auth flows, query one API. Neighbourhood stats, permit history, demographics, and energy all from api.neighbourly.io/v1/.
Build training datasets, AVMs, or investment models with clean, structured property features — permit activity, demographic profile, energy efficiency, environmental risk — all joinable on address_id.
Most real estate data APIs are US-first products with Canadian coverage bolted on. Neighbourly is built from the ground up for the Canadian market.
Talk to us about API access, data partnerships, or embedding Neighbourly in your product. Most teams are up and running within a day.
Common questions about this data and how to use it.
Addresses, neighbourhood boundaries, building permits, demographics, environmental context, and energy data for Canadian properties — all from a single REST API.
Yes. Address and property fields follow RESO conventions, so the data maps cleanly into MLS platforms, IDX feeds, and existing real estate schemas.
JSON for property and attribute data, with GeoJSON available for boundary and geometry endpoints.
Address and boundary layers cover all provinces and territories; permit, energy, and environmental layers roll out by region. See the coverage page for detail.
Pricing is usage-based, with no seat licences or long-term contracts. Contact us for an API key — most teams integrate within a day.