Improved Trips Accuracy for Split Loads

Release Date: June 17, 2025

What’s New?

To improve clarity and eliminate confusion in trip reporting, we’ve updated the behavior of the Trips endpoints when handling split loads.

What Changed?

When a load is split into sub-trips, the original (parent) trip is no longer returned via the API. Only the active sub-trips are included in the response.

If a load has not been split, the original trip is returned as usual.

Endpoints Affected:

GET /api/p/verion/trips

POST /api/p/verion/trips/search

Why?

Previously, both the original (parent) trip and its sub-trips were returned via the API. This could lead to duplicated mileage, carrier amounts, and other values in reports unless the parent trip was manually excluded.
With this update, only sub-trips are returned when a load is split — allowing customers to calculate totals (like mileage or carrier amounts) by simply summing all trips returned. This change improves accuracy in any report that relies on trip-level data.

❗️

Important Note

This change may impact metrics in your current reports — such as total trips, total mileage, total carrier rate, and others — starting today.

If your reporting logic includes custom filters or scripts to automatically exclude the original (dispatched) trip when a load is split, those filters may now be obsolete. Since the original trip is no longer returned, continuing to exclude it may result in underreporting.

Please review and update any custom reporting logic accordingly to ensure accurate totals going forward.