DCB Logistics REST API Platform

Enterprise transactional draft-save endpoint for the DCB OMS/TMS platform. This endpoint: • Validates incoming shipment data • Creates destination delivery sites • Saves draft waybills • Saves parcel information • Saves invoice references • Preserves operational shipment snapshots • Uses SQL transactional commit/rollback protection Current functionality: • Draft save only • No FreightWare push • No label generation • No parcel allocation • No finalization workflow The endpoint automatically: • Calculates shipment totals • Calculates volumetric weights • Calculates invoice totals • Creates destination site records • Links sites to company ownership structures Route: POST /api/DCBOnlineWaybillSave Required: • companyId • accountNumber • waybillNumber • divisionId • serviceTypeId • parcels Returns: • success status • saved waybill ID • waybill number • validation errors if applicable

Creates a FreightWare waybill.

Lookup postal code information using suburb name, postal code or both values together.

Returns POD PDF document from eDocs. Example: GET /api/pod?waybill=XXXXXXXXXXXX

Retrieves advanced FreightWare tracking details.

Returns a FreightWare quick quote estimate. REQUIRED HEADER: X-FreightWare : FreightWare Session Token Authentication: First call: POST /api/auth/login Then use returned token in the X-FreightWare request header.

Generate secure browser-accessible printable shipment labels including (X-FreightWare Required): • Route codes • QR codes • Parcel barcodes • Dimensions • Parcel weights • Consignee details • Waybill details REQUIRED HEADER: X-FreightWare : FreightWare Session Token FLOW: 1. Authenticate using: POST /api/freightwareauthentication/login 2. Use returned token in the X-FreightWare header 3. Call this endpoint to generate a temporary secure browser-accessible PDF label URL The returned URL expires automatically after 5 minutes.

Public shipment tracking endpoint. No authentication required.

Authenticates against FreightWare and returns a FreightWare session token. This token must be used in the X-FreightWare request header for all authenticated API requests. Example Header: X-FreightWare : YOUR_TOKEN Username and Password are automatically encrypted before being sent to FreightWare.