Trip Temperature & Required Equipment Fields Added to Trip Response Body

What’s New?

We’ve added two new fields to the Trips endpoints in the Public API: Temperature and RequiredEquipment. These fields provide visibility into temperature requirements and equipment specifications for each trip.

What Changed?

Previously, temperature requirements and normalized equipment requirements were not exposed in the Public API.

Now, the response includes the following new properties:

"Temperature": {
  "SetpointTemperature": 70.0,
  "SetpointTemperatureMax": 75.0,
  "ControlMode": "Start/Stop"
},

"RequiredEquipment": [
  "Reefer"
]

Temperature

The Temperature object represents the required temperature settings for temperature-controlled trips.

• SetpointTemperature – The required target temperature.
• SetpointTemperatureMax – Optional maximum temperature when a range is defined.
• ControlMode – Expected operational mode (Continuous or Start/Stop).

If no temperature requirement exists for the trip, this field will return null.

RequiredEquipment

The RequiredEquipment field is now returned as an array of equipment types required for the trip.

Examples:

"RequiredEquipment": ["Reefer", "Van"]
"RequiredEquipment": ["Van"]
"RequiredEquipment": ["Flatbed", "StepDeck"]

If no equipment requirement is defined, this field will return null.

Endpoints Affected:

• POST /api/p/{version}/trips/search
• GET /api/p/{version}/trips/{id}

Why?

These additions provide:

• Improved visibility into temperature-controlled trip requirements
• Structured equipment data for easier validation and integration
• Better support for compliance workflows and custom tracking applications

This update enhances clarity and integration capabilities while maintaining backward compatibility.