Guides
Changelog
Back to All
Improved

Public API Enhancements for Loads, Trips, Carriers, Tenders, and Core Response Schemas

9 days ago

What’s New?

We’ve delivered additional Public API improvements across loads, trips, carriers, tenders, and several existing response schemas. These changes improve sync reliability, expose more operational data, and make related endpoints more consistent.

What Changed?

Previously, several important fields and behaviors were either missing from the published schema, inconsistent between related endpoints, or not fully exposed to integrations.

Now, the Public API includes the following confirmed changes:

Loads

Load responses now include:

{
  "tenderId": "string | null",
  "requiredEquipment": [
    "Reefer"
  ]
}

In addition:

  • orphaned loads are now treated as non-existent
  • load search totals exclude abandoned loads with no trips
  • load document and note operations now return 404 for orphaned loads

Trips

Trip responses now include:

{
  "orderNumber": "string | null"
}

Trip sync behavior was also improved:

  • split or invisible trips can now be returned as isDeleted: true when includeDeleted=true
  • GET /p/v{version}/trips now supports includeDeleted
  • POST /p/v{version}/trips/search now allows updatedAtRange as the only filter
  • load references of type service_exception are now exposed
  • carrier payloads are aligned between single-trip retrieval and trip search

Carriers

Carrier search results now include carriers in DoNotLoad status, which were previously omitted even when they were referenced by trips.

Tenders

Tender request references[] objects now support a type field, enabling typed reference routing.

Additional response schema updates

The new schema also confirms additional response-model changes outside the payment-posting flows:

  • CarrierResponse now includes:

    • PaymentMethod
    • ExternalIds
    • FactoringCompany

  • DriverResponse, TruckResponse, and TrailerResponse now include:

    • LicenseCountry

  • FuelResponse now includes:

    • Description

  • FuelResponsePumpLocation now includes:

    • State

Trip rate schema updates

The trip rate-related schemas were expanded with additional structures and fields:

  • DriverRatePolicyResponse now includes:

    • CustomerLineHaulDeductionRate
    • PerMileRate
    • PerMileDeductionRate

  • PerLoadRate now uses a dedicated PerLoadRateDto

  • MileageRateDto now includes:

    • UseHighestTier

  • PerTripRateDto now includes:

    • Tiers
    • MileageType

  • PerTripRateDto.Rate is now marked as deprecated in the schema

Error-response documentation updates

The new schema also adds broader error-response documentation across many existing non-webhook endpoints:

  • 401 Unauthorized
  • 403 Forbidden
  • 429 Too Many Requests

Why?

These enhancements provide:

  • better load and trip sync reliability for polling integrations
  • clearer identification of tender-originated loads
  • better visibility into order linkage at the trip level
  • more complete carrier search results
  • stronger consistency between related trip endpoints
  • richer master-data payloads for carriers, drivers, trucks, trailers, and fuel records
  • more expressive trip rate schemas