Contains information licensed under the Open Government Licence – Ontario
Bait Management Zones API · Ontario

Where live bait can go, mapped in English and French.

The Neighbourly Bait Management Zones API returns Ontario's Bait Management Zone (BMZ) boundaries as GeoJSON, with zone codes and names in English and French. It includes the zone where using or possessing live baitfish is not allowed. Find the zone for any map view or location.

5 zonesEnglish & French namesMultiPolygon GeoJSONZone codesViewport queries
Get an API key → Book a demo
Sample recordLive API
Central BMZ
ZGA du Centre · bait_management_zone 1
Code
C
Zones
5
Names
EN / FR
NortheasternNorthwesternSouthernNo live baitfish
Zone boundariesBilingual namesZone codesArea & perimeterGeoJSON
Overview

What is a Bait Management Zone?

Ontario uses Bait Management Zones to limit how far live bait and baitfish can be moved, which slows the spread of invasive species and fish diseases. In general, bait has to be used in the zone where it was bought or harvested. The API holds five zones: Northwestern, Northeastern, Central and Southern, plus an area where using or possessing live baitfish is not allowed. Each has a code and English and French names.

Bilingual by default

English (bmz_name) and French (bmz_fr) names on every zone. No separate locale call is needed for Ontario's French-language users.

Includes the no-live-bait zone

The NLB zone marks where live baitfish cannot be used or possessed, which is the area anglers most need to know about.

Zone for any map view

Send a viewport and get the zones that cover it, with geometry if you want it.

Fields

What each record contains.

These are the fields the API returns for this layer. Field names match the JSON response exactly.

Field Type Description
id integer Stable Neighbourly zone ID
bmz string Zone code: C, NE, NW, S, NLB
bmz_name string English name, e.g. Central BMZ
bmz_fr string French name, e.g. ZGA du Centre
shapearea float Zone area (source units)
shapelen float Zone perimeter (source units)
bbox_west … bbox_north float Bounding box
boundary_geojson GeoJSON MultiPolygon geometry
Endpoints

Query by map view, ID or filter.

All requests go to https://api.neighbourly.io and send your key in the Api-Key header. A viewport is a JSON bounding box, {"southWestLat":…,"southWestLon":…,"northEastLat":…,"northEastLon":…}, URL-encoded.

GET
/api/v1/locations/bait_management_zone?viewport={…}&includes_boundaries=true
Zones overlapping a viewport, with optional geometry.
GET
/api/v1/locations/bait_management_zone/{id}
One zone with its boundary.
GET
/api/v1/spatial/bait_management_zones
All zones as a GeoJSON FeatureCollection.
Example response

Real data, straight from the API.

Live response, trimmed. NW and S follow the same shape.

  • GeometryMultiPolygon
  • FormatJSON and GeoJSON (WGS84, EPSG:4326)
  • CoverageOntario, Canada
  • SourceOntario Ministry of Natural Resources (Ontario GeoHub)
  • Per requestAll zones in one request
  • AuthApi-Key header
GET /api/v1/locations/bait_management_zone?viewport={Ontario} 200 OK 
[
  {
    "id":       1,
    "bmz":      "C",
    "bmz_name": "Central BMZ",
    "bmz_fr":   "ZGA du Centre"
  },
  {
    "id":       2,
    "bmz":      "NE",
    "bmz_name": "Northeastern BMZ",
    "bmz_fr":   "ZGA du Nord-Est"
  },
  {
    "bmz":      "NLB",
    "bmz_name": "No use or possession of live baitfish",
    "bmz_fr":   "Utilisation ou possession interdite de poissons d'appât vivants"
  },
  …
]
Who uses it

Where this layer earns its place.

Fishing apps

Bait rules where you fish

Tell users which bait zone they are in and warn them when a trip crosses into another zone or into the no-live-bait area.

Bait retailers

Zone-aware stores

Tag store locations with their BMZ so customers know the bait they buy can be used where they fish.

Government & conservation

Invasive-species outreach

Target bilingual outreach to anglers by zone, using the official names in both languages.

Tourism

Clear guidance for visitors

Add the bait zone to lake and lodge pages so out-of-area visitors arrive prepared.

Related layers

Works well with.

Every environmental layer shares the same API key, coordinate system and response conventions. Combine them in one integration.

Fisheries Management Zones APIAll 20 Ontario Fisheries Management Zone (FMZ) boundaries as GeoJSON. Wildlife Management Units APIWildlife Management Unit (WMU) boundaries as GeoJSON, with each unit linked to the counties and municipalities it overlaps. Fish Stocking Data APIOntario fish stocking records by lake. Aquatic Resource Data APIFisheries profiles for Ontario lakes and rivers. All environmental layersLakes, depth, fisheries, zones, Crown land, campgrounds and trails from one API.

Frequently asked questions

Common questions about the Bait Management Zones API.

What is a Bait Management Zone?

One of the zones Ontario uses to limit how far live bait and baitfish are moved, which helps prevent the spread of invasive species and fish diseases.

How many zones are in the API?

Five: Northwestern, Northeastern, Central and Southern, plus an area where using or possessing live baitfish is not allowed.

Are the names available in French?

Yes. Every zone has an English name (bmz_name) and a French name (bmz_fr).

Does the API include the bait rules?

No. It returns zone boundaries and names. Check the province's current bait regulations for what is allowed in each zone.

Where does the data come from?

Ontario Ministry of Natural Resources Bait Management Zone boundaries, published as open data.

How do I get access?

Request an API key from the dashboard or book a demo. Every request sends the key in the Api-Key header. Pricing is usage-based.

Data sources

Neighbourly normalizes public open data into one schema. Source licences and attribution apply; see our terms.

Add bait zones to your product.

Get an API key and query this layer today, or talk to us about coverage and volume.

Get an API key → Book a demo →