BrokerWare API Updates 11/05/2026

3PL API Updates

Added an optional isLocalTime=true query parameter to both GetLoads and GetLoad endpoints (Customer API and Client API).
- When set to true, date and time fields in the response are converted to your system’s local time zone (with no Z suffix) to match the shipment profile.
- Defaults to false (or omitted) to keep returning dates in UTC, ensuring full backward compatibility with existing integrations.
GetLoads and GetLoad now return the original estimated delivery date and time window (OriginalEstimatedDelivery, OriginalEstimatedDeliveryOpenTime, and OriginalEstimatedDeliveryCloseTime) alongside the active delivery window.
- Allows API users to distinguish between scheduled carrier delivery appointments and the original estimated delivery dates.

Fixed an issue where API-booked shipments failed during carrier tendering / e-dispatching due to an "invalid phone number" validation error.
Phone numbers stored in the database without formatting were rejected by carriers expecting formatted phone numbers.
Added automatic formatting logic to convert stored phone numbers into standard carrier-accepted formats prior to sending e-dispatch requests.

Added ServiceType and ServiceDescription fields to the carrier model (ShipmentCarrierApiModel) across both Customer and Client (broker) API GetLoads endpoints.
Enables customers to determine directly from API responses whether a delivery involves an appointment, allowing for accurate customer messaging without manual inquiries.
- ServiceType: Populated with the mapped service name, or a combination of ServicePriority and CarrierServiceType if no mapping exists.
- ServiceDescription: Populated with the mapped service description.
- Note: Returns null when no value is present.