Below is a summary of what our CargoWise integration expects of CargoWise for customers who have a piece of middleware that will sit between BravoTran and CargoWise.

If you have any questions feel free to email me at [email protected].

Inbound eAdapter

BravoTran uses the inbound eAdapter to

1. Fetch details about organizations, consols, shipments, customs declarations, and transports
2. Upload documents to eDocs
3. Post an invoice

Normally BravoTran can connect directly to the inbound eAdapter, however, if you have middleware set up for inbound as well, you need to provide a single endpoint that accepts XML for all of the above that uses HTTP basic authentication or OAuth.

Outbound eAdapter

BravoTran has two endpoints for accepting events emitted from the eAdapter depending on the format being sent to us. You would only use one of them.

Events

Use this endpoint if you are forwarding the original soap envelope to BravoTran.

https://api.bravotran.com/tms/cargowise/events?token=CHANGEME

Universal XML

Use this endpoint if you are unpacking the original soap envelope and forwarding the “unpacked” XML files.

https://api.bravotran.com/tms/cargowise/universal_xml?token=CHANGEME

Postman Collection

Our Postman collection has examples for what we send to the inbound eAdapter as well as what we expect from the outbound eAdapter.

CargoWise eAdapter Base – 2024-08-22.postman_collection.json