Retrieve GeoJSON polygon boundaries, real-estate-ready descriptions, character tags, FSA mapping, and linked demographics for any Canadian neighbourhood — by slug, ID, or coordinate. Built for listing platforms, neighbourhood search, and map-driven products.
Generic boundary datasets use census tract IDs and StatsCan codes. Neighbourly uses names and descriptions that buyers actually search for — with the GeoJSON polygon data your frontend map renderer needs.
Every neighbourhood name and description is written and reviewed by a human — not generated from census boundaries or Voronoi diagrams. They match what buyers type into search boxes and what real estate agents say to clients.
Every neighbourhood comes with a boundary GeoJSON MultiPolygon in SRID 4326 — ready to render in Mapbox, Leaflet, Google Maps, or any geospatial pipeline. Bounding box and centroid also returned.
Every neighbourhood has a stable slug like leslieville-toronto. Use it as your listing URL path, canonical route, or filter parameter — and resolve the full profile at any time via /v1/neighbourhood_by_slug/{slug}.
Look up a neighbourhood by slug, browse all neighbourhoods in a city, or resolve the neighbourhood from a lat/lng coordinate — every query returns the same rich profile object.
A neighbourhood profile response includes everything your listing platform, map renderer, or neighbourhood guide page needs — from the GeoJSON polygon to the curated description to linked census demographics.
{
"id": "nbhd_leslieville_tor",
"slug": "leslieville-toronto",
"name": "Leslieville",
"description": "Walkable east-end neighbourhood...",
"character_tags": [
"walkable", "family-friendly", "arts-culture"
],
"city": "Toronto",
"province": "ON",
"fsa": "M4M",
"centroid": {
"type": "Point",
"coordinates": [-79.3348, 43.6629]
},
"bbox": [-79.348, 43.655, -79.320, 43.671],
"boundary": {
"type": "MultiPolygon",
"coordinates": [[[...]]]
},
"_links": {
"demographics": "/v1/demographics/find?fsa=M4M",
"permits": "/v1/permits?neighbourhood_id=nbhd_leslieville_tor"
}
}
From "you're in Riverdale" on a listing detail page to full neighbourhood search-and-filter — the Neighbourly neighbourhood API powers the layer of context that turns a property address into a place.
Resolve the listing address to a neighbourhood at index time. Render the neighbourhood name, description, and character tags directly on the property detail page — giving buyers immediate location context without leaving your site.
Populate a neighbourhood filter or search dropdown from the /v1/neighbourhoods?city=Toronto endpoint. Use the slug as a stable URL segment — e.g. /listings/leslieville-toronto — for SEO-friendly neighbourhood search pages.
Fetch the GeoJSON boundary polygon and render it as a layer in Mapbox or Leaflet. Highlight the active neighbourhood on a listing map, or show boundary overlays in a neighbourhood comparison tool.
Generate a neighbourhood guide page for every Canadian city using the slug as a canonical URL, the description as copy, character tags as structured metadata, and linked demographics as stats. Scale content without scaling a writing team.
Common questions about this data and how to use it.
Neighbourhood boundary polygons in GeoJSON, profiles, URL-ready slugs, character tags, linked demographics, and walkability scores for any Canadian address.
Boundaries combine official and locally recognised neighbourhood definitions into consistent polygons, each with a stable ID and slug.
Yes. Query by address or lat/lng to get the containing neighbourhood, its boundary, and its linked data.
GeoJSON polygons, ready to render on a map or use in spatial queries.
Neighbourhood boundaries cover Canadian metro and urban areas and expand by demand. See the coverage page for a full breakdown.
Talk to us about API access, the full neighbourhood dataset, or embedding neighbourhood context into your listing or search product.