Skip to main content

Vehicle Store Integration

Erik Wihlborg
Updated

The purpose of the Vehicle Store integration is to enable a one-way synchronization of vehicles from the TSP to the Vehicle Store

Registering a fleet

Fleets must be registered in advance before it´s possible to upload vehicles.

POST /fleets

{
  "fleetId": "159032dc-e809-4a84-b5eb-15b4c0159138",
  "fleetName": "Ken Trucks Inc."
}

Uploading vehicles

POST /fleets/{fleetId}/vehicles

{
  "vehicles": [
    {
      "vehicleId": "740f410b-7f37-4dbc-9cc5-f7c160005dc7",
      "vin": "1GTHC23U62F244546",
      "vehicleName": "SPACE TRUCK 8459",
      "brand": "Volvo",
      "model": "VHD 300 AF"
    },
    {
      ... another vehicle
    }
  ]
}

Note: If a vehicle with the same Vehicle ID and Fleet ID already exists, it will be overwritten.

Updating or removing vehicles

// Updating a vehicle
PUT /fleets/{fleetId}/vehicles/{vehicleId}

// Removing a vehicle
DEL /fleets/{fleetId}/vehicles/{vehicleId}

Note: For a vehicle to be searchable in the TraX mobile app, it must exist in the Vehicle Store.

Implementation requirements and notes

We recommend a hybrid synchronization strategy that combines event-driven updates with scheduled full refreshes.

  • Event-driven updates are used to efficiently capture immediate changes.
  • Scheduled full refreshes are performed every 7 days to ensure the Vehicle Store remains fully synchronized with the TSP’s list of vehicles.

Vehicles are identified by a combination of fleetId and vehicleId. Using the same identifiers across both the SKF and TSP systems is essential to ensure that SKF can accurately notify the TSP which vehicle a device has been commissioned to (or decommissioned from).

The fleetId and vehicleID attributes are immutable and must not be changed. Both identifiers are provided by the TSP.
 

The POST /fleets/{fleetId}/vehicles operation is limited to 7,000 vehicles per request (approximately 1 MB of data).