Skip to main content

Expected Time to Dispatch (v2)

The POST /api/v2/recommended-price response now includes an estimated time-to-dispatch range, giving you a sense of how quickly a load is expected to book on the lane.

What's New in the v2 Response​

Two new fields are added to data:

  • min_expected_time_to_dispatch — lower estimate of how long the load is expected to take to dispatch (book), in hours, based on comparable recent moves on the lane.
  • max_expected_time_to_dispatch — upper estimate of the same, in hours.

Both fields are nullable and may be null when there is insufficient data for the lane. The change is additive — existing fields are unchanged, so no action is required to keep your integration working.

Example Response​

{
  "meta": { "status": "success" },
  "data": {
    "price": 1272,
    "price_per_mile": 0.88,
    "distance_miles": 1450,
    "volume": 42,
    "confidence": 69,
    "price_range_lower": 1150,
    "price_range_upper": 1400,
    "min_expected_time_to_dispatch": 1.5,
    "max_expected_time_to_dispatch": 6.0,
    "recent_moves": []
  }
}

Refer to the "Recommended Price (v2)" section in the Pricing Insights API reference for the full request and response schema.