BrokerWare API Updates 09/17/2026
3PL API Updates
Rating API
- Added support for returning carrier destination terminal details and driving distance to the consignee directly within rating responses, eliminating the need to assign a carrier or save a load beforehand. This will now pass the optional includeTerminalAddresses=true query parameter on rating requests. When enabled, each returned rate includes a destinationTerminal block containing the terminal name, code, address, contact information, and mileageFromConsignee.
CreateShipment API
- Resolved an issue where shipments created via the Create Shipment API lost their selected service level upon dispatch. Previously, API-created shipments stored only the service description rather than the service level itself, causing carrier dispatches to default to unselected service options.
Customer & Client APIs - Linked Loads Feature
- New Endpoints: Added POST LinkLoads and POST UnlinkLoads endpoints (available on Customer and Client APIs) to manage load relationships programmatically.
- Updated Responses: Added a linkedLoads array property to GetLoad, GetLoads, and Tracking responses.
- These changes apply to accounts with Enable Linked Loads turned on. For other accounts, nothing changes except that a new, empty linkedLoads field appears on load and tracking responses.
- Linked Loads - API
API endpoint for E-Dispatch
- Added ability to programmatically e-dispatch shipments using global or customer-specific API keys.
- Customer Endpoint: POST /api/clientv1/edispatch
- Global Endpoint: POST /api/v1/edispatch
- Requires loads to be in Booked Covered status to proceed. Otherwise, returns: "Load must be in booked covered status."
- Validates that the assigned carrier has e-dispatch enabled. Otherwise, returns: "Carrier is not e-dispatch enabled."
- Customer endpoint verifies that Allow Dispatch is set to Yes in customer preferences. Otherwise, returns: "Dispatch is not enabled for customer."
- Global endpoint includes raw carrier error response (carrierResponse) on failure. Sensitive carrier request parameters (carrierRequest) are omitted for security.