BC Data docs

drivebc_history

Historical DriveBC events (counts by year, month, district, type, subtype and road)

How many DriveBC road events (incidents, construction, road conditions, weather conditions, special events) had an update in each completed year 2018 to 2025: counts of event IDs updated in the year, grouped by year, month, district, event type, event subtype or road, from the province's Historical DriveBC Events data. Counts of DriveBC event IDs, not of crashes or separate closures. Filters are year range, type, district, severity (MINOR or MAJOR) or road (full name, any case, spelled as DriveBC wrote it), but only one extra dimension at a time. The current year is not included: use drivebc_events for now.

Cost: 1 unit of your allowance (see Rate limits).

Parameters

  • group_by (year, month, district, event_type, event_subtype, road, optional): default "year"
  • year_from (integer, optional): min 2018, max 2025
  • year_to (integer, optional): min 2018, max 2025
  • event_type (INCIDENT, CONSTRUCTION, ROAD_CONDITION, WEATHER_CONDITION, SPECIAL_EVENT, optional)
  • district (Lower Mainland District, Vancouver Island District, Rocky Mountain District, West Kootenay District, Okanagan-Shuswap District, Thompson-Nicola District, Cariboo District, Peace District, Fort George District, Bulkley Stikine District, Skeena District, optional)
  • severity (MINOR, MAJOR, optional)
  • road (string, optional): min length 1, max length 60
  • limit (integer, optional): min 1, max 100, default 25

REST

curl -X POST https://api.bcmcp.ca/v1/tools/drivebc_history \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

MCP

Call the tool drivebc_history with these arguments. Over raw JSON-RPC:

curl -X POST https://api.bcmcp.ca/mcp \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"drivebc_history","arguments":{}}}'

What comes back

Every answer is the same envelope, over REST and over MCP: available, data, citations, freshness and notes. See Citations and freshness.

On this page