Skip to main content

Temperature assets allocation API

This article explains how to allocate a main asset plus additional assets (for example: a trailer temperature sensor) to a transport via the TP Visibility Allocation API

A
Written by Anita Smielowska

In standard main asset allocation you could assign only one asset to a transport. With multi-asset allocation, you can keep the main vehicle allocation and additionally link other assets so their temperature data can be shown during transport timeslots.

When to use multi-asset allocation

Use it when:

  • the transport is already tracked with a primary vehicle, and

  • temperature data arrives from an additional device/asset that should be associated to the same transport.

Typical examples:

  • Truck (primary) + trailer reefer unit (additional asset)

  • Truck (primary) + extra temperature logger (additional asset)

  • Box Truck (primary) + trailer gps and temperature tracking system

Glossary

  • Primary asset - the main vehicle/device allocated to the transport, used primarily for GPS position tracking and, if included in the data flow, temperature data.

  • Additional asset - supplementary asset linked to the transport (for example: temperature device).

  • Multi-asset allocation - an allocation request that includes additional_assets.

API overview

The allocation API is available as a REST endpoint for transports. Multi-asset allocation extends the allocation request with an additional_assets array.

Endpoint: /transports/{identifier_type}/{identifier_value}/allocation

Data model

Each entry in additional_assets contains:

  • identifier (string): the additional asset identifier (for example License plate or device ID)

  • reason (string): why the asset is attached to the transport

Example payload

{ 
 "license_plate_number": "AB-123-XY", 
 "additional_assets": [ 
   { "identifier": "TEMP-003", "reason": "temperature" }, 
   { "identifier": "TEMP-002", "reason": "temperature" } 
  ] 
}

Important:

  • The vehicle (or equivalent primary allocation fields) represents the main allocated asset. It is the primary source of the vehicle GPS position for real-time tracking and, if temperature data also flows in the same data stream, it will be shown as well.

  • additional_assets is used for supplementary assets only (currently primarily for temperature use cases). Even if supplementary assets provide GPS position, it will not be used for transport tracking—only for temperature.

Allocate vs update vs remove

Allocate / update allocation

  • Send an allocation request for the transport including additional_assets.

  • If the transport already has a primary allocation, you can update it to include additional assets.

Remove additional assets

  • To remove additional assets, send an update where additional_assets is empty (or omitted), depending on your integration rules.

What you will see after successful allocation

  • Temperature data from the additional assets becomes available to be shown in the transport’s temperature view.

Troubleshooting

Common issues

  • 401/403 (Unauthorized/Forbidden): credentials/token missing or not allowed for this customer.

  • Transport not found / cannot allocate: verify the transport ID and that the transport exists in the environment.

  • Vehicle not found: ensure the primary vehicle identifier is valid/known for allocation.

What to provide when asking for support

  • Transport ID

  • Timestamp of the call (with timezone)

  • Full request payload (mask secrets)

  • Response status code + body

Did this answer your question?