Logistics API integrations, real time between your systems
Real-time, two-way connections between your TMS, WMS, webshop and the systems of your customers and carriers. Orders, statuses, track & trace and invoices are always up to date — no batch delays, no manual work.
Without obligation · reply within one working day
Always live, in both directions
A logistics API integration connects your system in real time with those of your customers, carriers and platforms. Where EDI often works in batches, an API synchronises immediately: a status update at the carrier is instantly visible to your customer. One single source of truth, always up to date.
We build and monitor these integrations, with secure authentication and automatic error handling, so they keep running day in, day out. More and more transport and warehouse software is built API-first, which often makes an API integration the shortest route between two systems.
What we connect in real time
- REST & webhook integrations
- Real-time status updates
- Track & trace forwarding
- Integration with portals & marketplaces
- Monitoring & automatic error handling
- Secure authentication (OAuth2)
One single source of truth that is always live — your customers and carriers see the same status as you, at the same moment.
Which logistics APIs we connect
Most modern transport and warehouse packages have an API. What is possible, and what you need to take into account, differs per package. We go into more detail on these packages:
- Qargo API integration — the API-first cloud TMS: create orders through the API, statuses back via webhooks.
- Mendrix integration — orders via Custom Link, everything else via the REST API and event webhooks.
- Picqer integration — the WMS with an open REST API and webhooks at every step in the warehouse.
- Smartroute integration — route planning with an API for orders and webhooks for statuses.
We also connect webshops and ERP packages to your transport, such as WooCommerce, Shopify, Magento, Lightspeed, Exact, AFAS, Odoo or SAP Business One. Virtually any system with an API or an export can be connected. How the warehouse and transport talk to each other is explained under integrating your TMS and WMS. If you subcontract trips to other hauliers, a carrier integration makes sure jobs and statuses travel back and forth automatically.
Webhooks or polling: how statuses come back in real time
There are two ways an API integration receives new information. With a webhook, the other system reports by itself that something has happened: a shipment has been loaded, an order has been planned, a parcel has been delivered. The status then reaches you and your customer within seconds.
If a system offers no webhooks, the integration asks at set intervals what has changed. That is slightly less immediate, but more than fast enough for most flows. We often combine both: webhooks for speed, plus a periodic check so that a missed message is still picked up.
How an API integration project runs
-
01
Mapping out
Which systems, which flows, and what the API of each package can do: endpoints, webhooks, limits and authentication.
-
02
Defining the fields
Which field in one system corresponds to which field in the other: references, addresses, service types and status codes.
-
03
Building and testing
We test with real orders from your environment and resolve discrepancies before anything goes live.
-
04
Go-live and support
After go-live we monitor the integration. If a message gets stuck, we usually spot it before you do.
How long it takes depends on the scope; a simple integration on a standard API can be done within a few weeks, larger projects take 1 to 3 months on average. You can read more about the steps under how we work.
An order from the webshop, straight into the planning in real time
Take a wholesaler that delivers its products with its own fleet. Orders come in through the webshop, are exported to Excel every morning and entered into the route planning by hand. Customers call to ask when their delivery will arrive.
-
01
As soon as an order in the webshop has been paid or released, the webshop reports it through a webhook. The integration retrieves the order and places it, with address, weight and requested delivery day, as an unplanned order in the TMS or route planner.
-
02
The planner plans as usual. Once the trip is fixed, the planned delivery date and time slot go back to the order in the webshop through the API, and the customer is notified automatically.
-
03
On the road, the driver app reports the status. On delivery, the status comes back to the order with a signature or photo, so customer service can see it and the invoice can be sent.
The result: no more morning export, no retyping, and customers who can see for themselves when their order will arrive. If you work with Smartroute, also read connecting Smartroute to your webshop.
Logistics API integrations in brief
When should I choose an API instead of EDI?
When you need real-time updates or are connecting with modern platforms and portals. For classic shipper–carrier flows, EDI is often the standard. We advise per partner; more on the difference can be found under what is EDI.
Can you connect my webshop or ERP to my transport?
Yes. Virtually any system with an API or an export can be connected, from WooCommerce and Shopify to Exact, AFAS or Odoo. Orders go to the planning automatically, and the delivery date and status come back into the webshop or ERP.
Can you connect to a platform I do not use yet?
Yes. If the platform has an API, we connect it. If not, we look for an EDI or file-based alternative.
How do you keep the integration reliable?
With monitoring, alerting and automatic retries. If something fails, we often see it before you do.
Ready to connect your platforms in real time?
Book an introductory call without obligation. Together we look at your systems and what an integration can deliver for you.