Gov Bc Ca APIs

9 APIs141 Endpoints4 Categories

API Catalog

BC Data Catalogue API

The BC Data Catalogue API provides programmatic access to the Province of British Columbia's open data catalogue, built on the open-source CKAN platform. It exposes search, package (dataset) listing, package detail, tag enumeration, and revision history endpoints, so applications can find authoritative BC government datasets and link to their distributions. Authentication is anonymous for read access and supports a CKAN API key for write or restricted operations. The catalogue covers thousands of provincial datasets across natural resources, transportation, demographics, and public services.

22 endpoints

BC Geographical Names Web Service - REST API

The BC Geographical Names Web Service exposes searchable, authoritative records for the official place names of British Columbia, including features such as lakes, rivers, mountains, communities, and parks. It serves the Province's gazetteer with endpoints for keyword search, official-only and not-official-only search, spatial 'inside' and 'near' search, recent name decisions, name change history, and detail lookup by name or feature ID. The service responds in multiple output formats and supports a feature taxonomy enumeration for filtering by feature class.

14 endpoints

BC Gov News API Service 1.0

The BC Gov News API Service exposes the published content stream of the British Columbia government newsroom, covering ministries, ministers, news releases, newsletters, editions, articles, and social media references such as Facebook posts. The API supports lookups by ministry key, by minister, and by newsletter or edition keys, and serves embedded image and asset endpoints needed to render news content in third-party properties. It is read-only over HTTPS and requires no authentication.

27 endpoints

BC Route Planner REST API

The BC Route Planner is the British Columbia government's routing engine for the province's public road network, computing shortest and fastest routes between a start point and one or more stops. It exposes pairwise distance, optimal route ordering, turn-by-turn directions, and a dedicated truck routing track that respects commercial vehicle restrictions. Output formats include JSON, GeoJSON, and KML, with 22 endpoints split across passenger and truck modes. Access is currently restricted to B.C. Government Ministries.

22 endpoints

DriveBC's Open511 API

DriveBC's Open511 API publishes real-time road events for British Columbia's public road network, conforming to the Open511 specification. Agents can query traffic accidents, construction zones, weather closures, and other roadwork events filtered by jurisdiction, geographic area, severity, and event type. The endpoint set covers four resources: events, jurisdictions, jurisdiction geography, and named areas, returning GeoJSON-style geometry alongside structured event metadata.

4 endpoints

Geocoder REST API

The BC Address Geocoder REST API cleans, corrects, completes, geocodes, and reverse geocodes British Columbia physical addresses, intersections, and the occupants associated with them. It exposes single-address geocoding, bulk autocomplete, and proximity searches such as nearest site, occupants near a point, and intersections near a point. Several endpoints accept a path-level outputFormat extension (such as .json or .geojson). Authentication is by API key passed in the apikey header.

16 endpoints

GeoMark Web Service REST API

The BC GeoMark Web Service creates and shares small geographic areas of interest as reusable, immutable web resources that can be retrieved in many file formats and coordinate systems. Once a geomark is created with POST /geomarks/new, the same geometry is exposed at /geomarks/{geomarkId} and supporting endpoints in formats such as GeoJSON, KML, and shapefile. This makes it easy to share an area of interest with people who use different mapping software without translating files manually. The service is read-mostly after creation, anonymous, and returns the bounding box, full feature, parts, and a representative point for each geomark.

7 endpoints

Groundwater Wells, Aquifers and Registry API

The Groundwater Wells, Aquifers and Registry (GWELLS) API exposes the British Columbia provincial register of groundwater wells, mapped aquifers, and qualified well drillers and pump installers. It serves codes for aquifer materials, productivity, vulnerability, and water use, plus listings and detail records for individual aquifers. Authentication is by JWT bearer token in the Bearer header for write operations, while many lookup endpoints are read-only over HTTPS. The dataset supports water security planning, drilling industry oversight, and applications that surface authoritative groundwater information to the public.

24 endpoints

WorkBC Job Posting API

The WorkBC Job Posting API exposes a feed of job postings published on the WorkBC Job Board run by the British Columbia government. It also serves the supporting reference data — major projects, job types, regions, and industries — that callers need to filter the feed sensibly. Job postings are retrieved with POST /jobs and matched against the supplied filters in the request body. The API is intended for partners syndicating BC public-sector and broader provincial job listings into their own employment portals or analytics pipelines.

5 endpoints

Connect Your Agent

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.