See what the Kuehne & Nagel LTL integration can do →
Integrate iPaaS.com with Kuehne+Nagel to enable seamless data synchronization for shipment tracking information.
How to Connect
Prerequisites
Access to the Kuehne+Nagel API is not open by default — it must be requested and approved before the integration can connect.
Email the Kuehne+Nagel Helpdesk at helpdesk@ec.kuehne-nagel.com to request API access. Include your Company Name, Contact Name, Phone Number, Email Address, and the Purpose of API Usage — for this integration, shipment tracking.
The Helpdesk returns an Authentication ID and a Client Code. Both are required on every call the integration makes.
Access may be subject to approval or to regional limitations depending on your service agreement. If your request is not granted, contact the Helpdesk directly.
Configuration Details
Gather these four values before configuring the subscription in iPaaS.com:
API Url: the address of the Kuehne+Nagel API the integration calls. Example:
https://api.ltlp.kuehne-nagel.com/apiUserName: the user ID you use to sign in to the Kuehne+Nagel website. Example:
acme-logisticsClient_Code: the client code issued by the Kuehne+Nagel Helpdesk when API access is approved. Example:
AB100Authentication_Id: the unique identifier issued by the Kuehne+Nagel Helpdesk alongside the client code. It is a GUID. Example:
3F2504E0-4F89-11D3-9A0C-0305E82C3301
Treat the Client Code and Authentication ID as credentials. Store them only in the iPaaS.com subscription settings and do not share them outside your organization.
Configure Subscription Settings
Navigate to the Kuehne+Nagel subscription in iPaaS.com and complete the fields below.
Field | Description | Required | Example |
Name | A unique name for this subscription within your company. | Yes |
|
Versions | The integration version this subscription runs. | Yes |
|
Create Default Mappings | Shown when the subscription is first created. When selected, the subscription starts with the default mapping collection and its mappings already in place. Leave it selected unless you intend to build every mapping yourself. | No | Selected |
API Url | The address of the Kuehne+Nagel API the integration calls. | Yes |
|
Authentication_Id | The unique identifier issued by the Kuehne+Nagel Helpdesk. | Yes |
|
Client_Code | The client code issued by the Kuehne+Nagel Helpdesk. | Yes |
|
UserName | The user ID used to sign in to the Kuehne+Nagel website. | Yes |
|
API Throttle Limit | Maximum number of calls the integration may make to Kuehne+Nagel within each throttle window. | Yes |
|
API Throttle Limit (To iPaaS) | Maximum number of calls made into iPaaS.com within each throttle window. | Yes |
|
API Throttle Seconds | Length of each outbound throttle window, in seconds. | Yes |
|
API Throttle Seconds (To iPaaS) | Length of each inbound throttle window, in seconds. | Yes |
|
Concurrent Batch Executions | Number of batch operations that may run at once. This integration does not batch its calls, so the value has no additional effect here. | Yes |
|
Concurrent Connections | Number of simultaneous connections the subscription may use. | Yes |
|
Webhook API Key | Generated by iPaaS.com and used to authenticate inbound webhook calls. Kuehne+Nagel does not send webhooks to iPaaS.com, so this integration does not use it. | No | Generated automatically |
The six throttle and concurrency fields are required, but they arrive pre-populated — see Throttling below before changing them.
Authentication Methods
Kuehne+Nagel authenticates each request using the three values issued to you, rather than a token exchange or a sign-in redirect. There is no authorization header and no token to refresh — the three values travel in the body of every request the integration makes.
Enter the UserName, Client_Code, and Authentication_Id in the subscription settings, together with the API Url. The integration sends all three with every request it makes to Kuehne+Nagel; if any of them is missing or wrong, Kuehne+Nagel rejects the request and the failure appears in Dashboard / Integration Monitoring / Error Logs.
Because the credentials are validated by Kuehne+Nagel only when a request is actually made, saving the subscription settings does not by itself confirm that they are correct. To confirm the connection, run a Manual Sync for a known shipment and check that it completes — see the Kuehne+Nagel to iPaaS.com Transaction Tracking Number Mapping Documentation for the identifier format to enter.
To rotate either credential, request a replacement from the Kuehne+Nagel Helpdesk and update the corresponding field in the subscription settings. No other change is needed.
Initialization Support
Currently, initialization is not supported for Kuehne+Nagel in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process. The Initialize Data section of the Subscription Settings page reflects this and offers no action.
Because there is no initialization mode, an existing backlog of shipments is not loaded when the subscription is first connected. To bring a large set of historical shipments in at once, use bulk sync using Postman.
Throttling
Throttling ensures that the Kuehne+Nagel API isn't overwhelmed by excessive API calls, preserving system performance during heavy data transfers.
While the throttling fields are required, the values are pre-populated by the integration settings. Kuehne+Nagel does not publish call limits for this API, so the shipped values are a conservative starting point rather than a match to a documented quota. Reduce them if you encounter rate-limit errors. If you run large catch-up polling jobs, stagger them rather than running them alongside other intensive processes.
For more details, refer to Subscription Configuration – Edit.