Brokerware API Updates

3PL API Updates

Shipment API - Linear Feet

• Shipments created via API now automatically calculate and store linear feet values using the same business logic applied in the front-end UI (when enabled by system defaults).
• Enabled across all shipment creation endpoints, including:
  • /api/v1/createshipment
  • /api/v1/createshipmentwithratequoteId
  • /api/clientv1/createshipmentAPI
  • /api/clientv1/createshipmentwithratequoteID

Claim Documents API

• Introduced a new global API endpoint allowing users to upload documents directly to active carrier claims on a load. - POST /api/clientv1/CreateClaimDocument
• Carrier Claim Validation: Documents are automatically attached to the matching carrier claim on the specified load. If no matching active claim exists for the provided carrier (carrierId, carrierScac, carrierName), the API returns a 400 Bad Request error ("No claim found on load [loadId] for carrier [carrierName] ([carrierScac]).").
• Supported Document Mapping: Mapped standardized document types to system categories with default public visibility. Supported types include BOL, Carrier Bill, Carrier Packet, Claim, CreditApp, Delivery Order, Detention, Dispatch, Document Packet, Insurance Doc, Invoice, LOA, Lumper, Packing Slip, Photo, POD, PO, Quote, Reclassification, Scale, Vendor Docs, Weight Insp, CSV, Excel, Word, Other, and more.
• Create Claim Document

UpdateShipment API

• Added the PickupNumber field to all UpdateShipment and UpdateShipmentAdvanced global and customer-specific API endpoints.
• Ensured existing requests omitting PickupNumber remain fully backward compatible without requiring API version updates.
• Updating the pickup number automatically generates an internal audit note on the shipment.