Connect the Qargo API to your supply chain
We connect Qargo TMS via the Qargo API to the systems of your customers, carriers and platforms — API-first and in real time, with support and maintenance included.
Without obligation · reply within one working day
Qargo connected to the rest of your supply chain
Do you use Qargo TMS? As a modern, API-first cloud TMS, Qargo lends itself very well to real-time integrations. We connect Qargo to the systems of your customers, carriers and platforms, so orders, status updates, documents and invoices flow through automatically: designed, built and monitored.
We have previously built Qargo API integrations, EDI integrations and outgoing webhooks that run in production. So we know how the Qargo API behaves in practice, not just what the documentation says.
We integrate Qargo mainly via API, and via EDI where a partner asks for it. See also our TMS & WMS integrations.
What Qargo offers for an integration
Open API for orders
Create and update transport orders, and request their status. An existing order can serve as a template for new orders, which is handy for recurring trips.
Webhooks for status updates
Qargo forwards events to an external system itself as soon as they happen. So your customer hears straight away when a shipment has been loaded or delivered, without anyone having to ask.
Passing orders on to subcontractors
Qargo can forward subcontracted trips to a third party via a webhook. That means a subcontractor without an integration of its own can still be connected automatically.
Trips, documents and invoices
Retrieve trip information, download documents such as the signed POD, and pass invoices on to your accounting system: it can all be done through the same API.
What we connect to Qargo
- Orders from shippers into Qargo. Via EDI (IFTMIN), the shipper’s API, or from Excel, CSV and email. See also importing orders without EDI.
- Status updates and POD back to the customer. In their own format: IFTSTA, an API call or a file.
- Trips to subcontracted carriers and subcontractors, and their status updates back into Qargo. See carrier integration.
- Qargo linked to a WMS, so orders that are ready to ship appear on the planning board automatically.
- Invoices to your accounting system or to the customer, for example as INVOIC.
What to plan for with Qargo
Every package has its own rules. These are the points that, with Qargo, make the difference between an integration that keeps running and one that stalls every now and then. We take them into account from day one.
An approved integrator is required
API access to Qargo runs via an integration ID from an integrator approved by Qargo. We take care of that application and the coordination with Qargo.
Webhooks are set up by Qargo
The credentials for webhooks are issued by Qargo itself. Allow a few days for this in the planning.
Service types must match
An order only comes in correctly if the transport service type in the message exists in your Qargo environment. We agree the list with you in advance.
Much is available as standard
Qargo itself already has many ready-made integrations and EDI message types. We first look at what is possible as standard, and only build what is missing.
A shipper sends orders, Qargo sends status updates back
Take a carrier that receives transport orders every day from a large shipper, as an EDIFACT message over SFTP. The planner enters them into Qargo by hand, and status updates go back by email.
-
01
The shipper’s IFTMIN is collected and translated into an order in the Qargo API, with the right service type and the right loading and delivery times.
-
02
The planner sees the order on the planning board straight away. Changes and cancellations from the shipper update the same order instead of creating a second one.
-
03
On loading and delivery, Qargo sends a webhook. We turn it into an IFTSTA for the shipper, with the signed POD attached as soon as it is available.
The shipper’s orders appear in Qargo without retyping, and the shipper sees the status as soon as the driver marks it as completed.
Arian Masselink, Enschede
I own Transportkoppeling and build the integrations myself. So you don't talk to an account manager, but directly to the person who designs and builds your Qargo integration and then keeps an eye on it.
Using Qargo? Call Arian.
You speak straight away to the person who builds your integration. No salesperson and no call centre: within ten minutes you know whether and how your integration can be done.
Or email contact@transportkoppeling.nl
Useful to have to hand
- Which version of Qargo you use
- Which customer, carrier or system you want to connect to
- How it works today: email, Excel, a portal or retyping by hand
Qargo integration in brief
Which partners do you connect Qargo to?
Any shipper, carrier or platform with an API, and via EDI where needed. We connect Qargo to the partners you work with.
Is it standard or custom-built?
Qargo has a lot on board as standard. We add to it where a partner or situation asks for something Qargo cannot do out of the box, and we look after the whole.
Do I need to arrange anything with Qargo myself?
Very little. You give permission for the integration with your Qargo environment; we handle the technical coordination with Qargo, such as the integration ID and the webhooks.
Who looks after the integration once it is live?
We do. We monitor the integration proactively, so it keeps running day in, day out.
Other packages we integrate
Connect Qargo to your supply chain?
Book an introductory call without obligation. Together we look at your systems and partners, and at what an integration will deliver for you.