Changelog
June 2, 2025 - API v4 release
What's new
- New holidays service - retrieve the dates when Winnipeg Transit is operating different service due to a holiday.
- New trip schedules service - retrieve the schedule for a specific trip that a bus travels along a variant.
-
New attributes for routes, stops, trips, and variants:
-
effective-from- indicates when service on a route, stop, trip or variant begins. -
effective-to- indicates when service on a route, stop, trip, or variant ends.
-
-
New parameters:
-
effective-on- for destinations, routes, stops, trips, and variants services. Allows querying for service at a specific date and time. -
json-camel-case- convert JSON keys in results to camel case. Future versions will make this behaviour the default for JSON results.
-
Changes and fixes
- Fixed bug where querying for stop schedules around a schedule change transition would return an array of duplicate stop results. This now always returns a single stop result.
-
In JSON results in v3 and below, integer values were returned as integers, but floating point numbers (e.g., distances and coordinates) were returned as strings. Now all numeric values are returned as numbers.
For example, what was previously returned like:
{ "stops": [ { "key": 10064, "distances": { "direct": "60.54" } }, { "key": 10002, "distances": { "direct": 59 } } ] }Will now be returned like:
{ "stops": [ { "key": 10064, "distances": { "direct": 60.54 } }, { "key": 10002, "distances": { "direct": 59 } } ] }