Stable identifiers
Every shipment, booking and invoice carries a durable reference. Both sides agree which system owns each identifier and never reuse one.
How Intelicargo exchanges data with your systems: the principles we follow and the questions we settle with your technical team before anything goes live.
Every shipment, booking and invoice carries a durable reference. Both sides agree which system owns each identifier and never reuse one.
Integration access is granted per partner with scoped credentials that are kept out of browser code and rotated on a schedule you control.
Writes carry an idempotency key so a retried message never creates a duplicate booking or a second invoice.
REST-style requests for on-demand data, event notifications for status changes and EDI or file exchange for partners who work that way.
Separate test environments and representative records let both teams validate mappings and failure handling before real cargo depends on them.
Every exchange is logged so finance and operations can reconcile what was sent, what was received and what needs attention.
# Illustrative request only, not a public API specification POST /integrations/bookings Content-Type: application/json Idempotency-Key: 6c1e… { "customer_reference": "PO-58213", "origin": "Port Everglades", "destination": "San Juan", "items": [{ "pieces": 4, "volume_ft3": 127 }] } → 201 Created · status: Hold · operator review required
Let’s map the workflow, find the friction and build the right connection.