Build on /v1 without worrying that it will change under you. It only ever gains things. Anything that could break an integration ships as /v2, with at least 90 days' notice before /v1 is retired.
These changes can ship at any time. Each one is listed in the changelog below.
These would break an existing integration, so they never happen in /v1. They ship under a new path, and /v1 keeps working unchanged alongside it until its retirement date.
reason, label, disclaimer). Weather alerts are still shown exactly as issued./v1, or any part of it, is retired. /v2 is available for that whole time so you can test against it.available: false or moves to check_source) and tell you as soon as we know, with the reason.hazards entries on free keys, because the source licence does not allow redistribution. Free keys now get a check_source entry for fire_bans, the same link partner keys already receive. Partner payloads are unchanged.GET /v1/conditions with lat, lon and an optional date, authenticated with X-API-Key. Points must be inside British Columbia.get_conditions.verdict (verdict_version 3), weather, forecast_3day, hazards, access, check_source for avalanche, fire bans and tides, briefing_url, conditions_url, attribution and disclaimer, as described on the partner page.401 for a missing or bad key, 429 over a limit, 422 for a missing or malformed lat / lon. A point outside BC or an unusable date returns 200 with an error field.