The GET alerts/incidents/stream endpoint has some new features! The following options have been added to the details field:
The GET assets endpoint has some new features! Added an optional includeAttributes query parameter that, when set to true, returns the list of attributes associated with each asset in the response.
The GET ridership/route-setups/.routeId endpoint has some new features! The routeId path parameter now accepts either a Samsara ID or an external ID in key:value format (e.g. extRoute:WB-12). Existing callers using numeric IDs are unaffected.
The PUT ridership/route-setups endpoint has some new features! routeId, passengers[].passengerId, passengers[].pickUpStopId, and passengers[].dropOffStopId now accept either a Samsara ID or an external ID in key:value format. Existing callers using numeric IDs or UUIDs are unaffected.
The POST ridership/route-setups endpoint has some new features! routeId, passengers[].passengerId, passengers[].pickUpStopId, and passengers[].dropOffStopId now accept either a Samsara ID or an external ID in key:value format. Existing callers using numeric IDs or UUIDs are unaffected.
The DELETE ridership/route-setups endpoint has some new features! The routeId query parameter now accepts either a Samsara ID or an external ID in key:value format (e.g. extRoute:WB-12). Existing callers using numeric IDs are unaffected.
The GET dvirs/stream endpoint has some new features! The authorSignature, secondSignature, and thirdSignature objects now include an optional externalIds field when the signer is a driver with an external ID configured.
The GET dvirs/.id endpoint has some new features! The authorSignature, secondSignature, and thirdSignature objects now include an optional externalIds field when the signer is a driver with an external ID configured.
The GET fleet/routes endpoint has some new features! We added tagIds as an optional query parameter to allow filtering routes by tag IDs. A route is included if it has the tag, or its assigned driver or vehicle is on that tag.
The POST functions-storage/files endpoint is now in the Beta stage. Feel free to send in your comments via our feedback form. (Note this endpoint should not be used in production until it is made generally available).
