Before You Begin
Access to the Kuehne+Nagel API is not open by default. It must be requested and approved before the integration can connect, so start this step early — the credentials it returns are required to finish the setup.
Email the Kuehne+Nagel Helpdesk at helpdesk@ec.kuehne-nagel.com and include:
Company Name
Contact Name
Phone Number
Email Address
Purpose of API Usage: for this integration, shipment tracking
The Helpdesk returns two values:
Authentication ID
Client Code
Both are required on every call the integration makes to Kuehne+Nagel. You will also need the user ID you use to sign in to the Kuehne+Nagel website.
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.
Installation Instructions for Integration Setup
Go to Subscriptions and click Search Certified Integration Marketplace & Subscribe.
Find and click the Kuehne+Nagel integration tile. The marketplace lists it as Kuehne & Nagel.
Review the integration details, then click SUBSCRIBE. The Supported Flows table on this page confirms what the integration transfers — a single Transaction Tracking Number flow, driven by a polling event.
Enter a Name for the subscription and select a Version. The name can be anything relevant and unique within the company the subscription is created in.
Format: [Product Name] - [Environment/Purpose]
Example: Kuehne+Nagel - Production
Leave Create Default Mappings selected. This creates the subscription with the shipment tracking mapping collection and its mappings already in place. Clear it only if you intend to build every mapping yourself.
Enter the API URL for your Kuehne+Nagel subscription:
Production:
https://api.ltlp.kuehne-nagel.com/api
Kuehne+Nagel does not provide a separate sandbox host for this service, so the same address is used in every environment.
Enter your Kuehne+Nagel website login user ID at USERNAME.
Enter the CLIENT_CODE provided by the Kuehne+Nagel Helpdesk.
Enter the AUTHENTICATION_ID provided by the Kuehne+Nagel Helpdesk.
Review the throttling and concurrency values. These arrive pre-populated by the integration and rarely need changing at install time — see Operational Configuration below.
Click Apply to save the settings.
Authentication Configuration
Kuehne+Nagel authenticates each request from three values you entered above, sent together on every call. There is no separate authorization step to complete, no consent screen, and no token that needs refreshing.
Credential | Where it comes from | What it is used for |
AUTHENTICATION_ID | Issued by the Kuehne+Nagel Helpdesk when API access is approved. | Identifies your organization to the Kuehne+Nagel API on every request. |
CLIENT_CODE | Issued by the Kuehne+Nagel Helpdesk alongside the Authentication ID. | Identifies the account whose shipments the integration may read. |
USERNAME | The user ID you use to sign in to the Kuehne+Nagel website. | Identifies the user the requests are made on behalf of. |
Important Notes
These credentials are not obtained from a Kuehne+Nagel web page — they are supplied by the Helpdesk in response to your access request, so there is no screen to copy them from. Keep the Helpdesk's reply somewhere secure.
Kuehne+Nagel checks the credentials only when a request is actually made. Saving the subscription settings does not confirm they are correct — verify them using the data sync test below.
To rotate either credential, request a replacement from the Helpdesk and update the matching field in the subscription settings. Nothing else needs to change.
Operational Configuration
The throttling and concurrency fields arrive pre-populated and are required, so leave them populated even if you do not intend to tune them.
Field | What it controls | Purpose |
API THROTTLE LIMIT | The maximum number of calls the integration may make to Kuehne+Nagel within each throttle window. | Keeps request volume within what the Kuehne+Nagel account can comfortably serve. |
API THROTTLE SECONDS | The length of each throttle window, in seconds. | Sets the period the limit above is measured over. |
API THROTTLE LIMIT (TO IPAAS) | The maximum number of calls made into iPaaS.com within each window. | Bounds the rate at which tracking records are written. |
API THROTTLE SECONDS (TO IPAAS) | The length of each inbound window, in seconds. | Sets the period for the inbound limit. |
CONCURRENT CONNECTIONS | How many requests may be in flight at once. | Controls how aggressively a polling run works through its shipments. |
CONCURRENT BATCH EXECUTIONS | How many batch operations may run at once. | Has no additional effect for this integration, which does not batch its calls. |
Recommended values
Initial setup: leave every field at the value the form supplies. The shipped values are deliberately conservative and are appropriate for a first connection.
Ongoing operations: no change is normally needed. Kuehne+Nagel does not publish call limits for this API, so there is no documented quota to tune towards.
If you see rate-limit errors: reduce API THROTTLE LIMIT and CONCURRENT CONNECTIONS rather than increasing them, and stagger large catch-up polling runs instead of running them alongside other intensive processes.
For a full reference on each field, see Kuehne+Nagel Connections and Settings.
Post-Installation Verification
Data Sync Test
This integration brings shipment tracking into iPaaS.com; it does not send anything to Kuehne+Nagel, so there is no outbound test to run.
Identify a Kuehne+Nagel shipment whose Reference Number matches the Transaction Number of an order already in iPaaS.com.
Go to the Manual Sync page and run a sync for that shipment, entering its identifier as the Bill of Lading number and carrier SCAC code joined by a pipe character — for example KN123456789|KUEH.
Open the Transaction in iPaaS.com and confirm a tracking record has appeared, carrying the tracking number and the shipment's current status.
A failure here is the first real confirmation of whether the credentials are correct. If the sync fails, check Dashboard / Integration Monitoring / Error Logs and see the Error Messages article linked below.
Functionality Test
Confirm that a Shipping Method matching the one in the shipped mapping exists in iPaaS.com — without it, transfers fail. See the mapping documentation linked below.
Enable the shipment/poll event and set its schedule, then confirm that shipments updated since the last run transfer automatically on the next scheduled run.
Change a shipment's status in Kuehne+Nagel, transfer it again, and confirm the existing tracking record updates rather than a second one appearing.
Review the logs in iPaaS.com to confirm the transfers completed as expected.
Error Messages
Errors raised during setup and during transfers, with their causes and resolutions, are catalogued in the Kuehne+Nagel Error Messages article linked below. The two most common at install time are a shipment identifier entered in the wrong format, and a shipment whose Reference Number has no matching iPaaS.com Transaction.
Support and Troubleshooting
For issues with iPaaS.com
Click the Help button on any iPaaS.com page to contact Support or to search the documentation.
Support Portal: https://support.ipaas.com/en/
Contact Information: https://ipaas.com/contact-us/
For issues with Kuehne+Nagel
Helpdesk (API and technical support): helpdesk@ec.kuehne-nagel.com, the same address used to request API access. Use it for authentication problems, access that has lapsed, and questions about shipment data.
LTL Plus portal:
https://my.ltlp.kuehne-nagel.com, for account administration.General enquiries: https://home.kuehne-nagel.com/
Kuehne+Nagel does not publish API documentation for this service publicly; endpoint details are supplied by the Helpdesk when access is granted. Support arrangements vary by region and service agreement — confirm yours with your local Kuehne+Nagel representative.