Guides
Changelog
Back to All
Added

Check Calls Now Available in the Public API

11 days ago

Release Date: July 10, 2026

What's New?

Check calls — driver status updates recorded against a trip — can now be read and logged through the Public API. Tracking platforms and visibility providers can push location updates into Alvys and read back the full check-call history without manual entry.

What Changed?

Previously, check calls were only visible and editable inside the Alvys platform.

Now, the Public API includes two new endpoints:

GET  /api/p/v{version}/trips/{tripId}/check-calls
POST /api/p/v{version}/trips/{tripId}/check-calls
  • List trip check calls — returns every check call recorded on the trip.
  • Log a trip check call — records a new check call with a required description plus optional activity, driverId, structured location (coordinates included), and reefer setpointTemperature / returnTemperature.

Response Body Includes

  • Core: Id, LoadNumber, TripId, TripNumber, Description
  • Status: Activity, ResponseType, DriverName
  • Location: structured address with coordinates
  • Reefer: SetpointTemperature, ReturnTemperature
  • Audit: CreatedAt, CreatedBy

Unset optional fields are returned as null (not empty strings), so consumers can distinguish "not provided" from "explicitly empty".

Why?

Check calls are the heartbeat of in-transit visibility. Exposing them via the Public API lets tracking integrations write status updates directly to the trip and lets downstream systems consume a single, consistent history.