Migration v1 → v2
legacyFor partners migrating from the v1 API. If you're building a new integration, skip this page.
Authentication: bearer token removed
v1 required
POST /authentication to obtain a JWT bearer token, then passing Authorization: Beareron every call, with refresh logic. v2 replaces all of that with two static headers.Endpoint URL changes
| v1 | v2 |
|---|---|
| POST /authentication | Removed |
| GET /v1/company-info | GET /v2/company-info |
| GET /v1/drivers | GET /v2/drivers |
| GET /v1/driver/{driverId} | GET /v2/driver/{driver_id} |
| GET /v1/latest_driver_status | GET /v2/latest-driver-status |
| GET /v1/vehicles | GET /v2/vehicles |
| GET /v1/vehicle/{vehicleId} | GET /v2/vehicle/{vehicle_id} |
| GET /v1/latest_vehicle_status | GET /v2/latest-vehicle-status |
| — (not available) | GET /v2/vehicle-location-history/{vehicle_id} |
Field renames
camelCase → snake_case across every parameter and response field.
| v1 | v2 |
|---|---|
| companyId | company_id |
| driverId | driver_id |
| vehicleId | vehicle_id |
| firstName | first_name |
| currentStatus | current_status |
| VIN | vin |
Pagination & IDs
v1 used skip + limit. v2 uses page (1-indexed) +limit. Responses now includepage, size,total_elements,total_pages.
All entity IDs migrated to UUID. Old-format IDs are still accepted in path parameters but responses always return UUID. To remap stored IDs, match by username (drivers) orvin (vehicles).