Overview
This article catalogs the error messages the Kuehne+Nagel integration can record in the iPaaS.com error logs, grouped by the mapping collection flow that raises them. Each entry carries a stable error code, the message as it appears in iPaaS.com, what causes it, and how to resolve it. The code stays the same even if the wording changes, so you can search this page for the code shown in your error log to find the matching entry. Errors appear in Dashboard / Integration Monitoring / Error Logs.
Some resolutions refer to your Managed Integration Service Provider (MiSP) — the partner who configured and manages this integration for you. Your MiSP owns the mapping configuration, the subscription settings and credentials, and the reconciliation between Kuehne+Nagel shipments and iPaaS.com Transactions, so they are the right first contact for anything you cannot correct in your own data.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Some conditions that stop a transfer are configuration requirements rather than error messages in their own right — most notably the requirement that the shipping method mapped by this integration already exists in iPaaS.com. Those are covered in the Kuehne+Nagel to iPaaS.com Transaction Tracking Number Mapping Documentation and in the mapping collection description, alongside the setup steps that prevent them.
Supported Flows
Add/Update Kuehne+Nagel Transaction Tracking Number TO iPaaS.com
Error Collection
Add/Update Kuehne+Nagel Transaction Tracking Number TO iPaaS.com
Invalid Shipment Identifier
KUNA-VALD-1001 - Could not transfer because the Shipment Id was not provided in the correct format. Expected format: {BlNumber}|{Scac}
Description: The shipment identifier supplied for the transfer is not in the form the integration expects. It occurs most often on a Manual Sync where the value entered is missing the pipe separator, is missing one of the two parts, or has extra spacing. The transfer stops before any call is made to Kuehne+Nagel.
Resolution: Re-enter the identifier as the Bill of Lading number and the carrier SCAC code joined by a pipe character, with nothing either side of it — for example KN123456789|KUEH. Both parts are required.
Missing Reference Number
KUNA-VALD-1002 - Could not transfer because the Kuehne+Nagel shipment has no Reference Number. Shipment Id: {ShipmentId}
Description: Kuehne+Nagel returned the shipment, but the record carries no Reference Number. The integration uses the Reference Number to find the iPaaS.com Transaction the tracking record belongs to, so without it there is nothing to attach the shipment to. The message names the shipment identifier that failed, so you can identify the shipment directly from the log entry.
Resolution: Add the Reference Number to the shipment in Kuehne+Nagel so that it carries the order reference used in iPaaS.com, then transfer the shipment again. If the shipment legitimately has no order reference, it cannot be tracked against an iPaaS.com Transaction and should be excluded from the transfer.
No Matching Transaction
KUNA-NFND-1001 - Could not transfer because no iPaaS.com Transaction has Transaction Number {ReferenceNumber}. Kuehne+Nagel Shipment Id: {ShipmentId}
Description: The shipment carries a Reference Number, but no iPaaS.com Transaction has a Transaction Number matching it. The match is exact — a difference in case, spacing, or leading zeros is enough to prevent it. The message names both the Transaction Number that was searched for and the shipment identifier that failed.
Resolution: Confirm the Transaction exists in iPaaS.com and that its Transaction Number matches the shipment's Reference Number exactly, then transfer the shipment again. This integration never creates the Transaction — it only attaches tracking to one that is already present, so the Transaction must be transferred into iPaaS.com first by whichever integration owns it. If the Transaction is present and the numbers look identical but the match still fails, ask your Managed Integration Service Provider (MiSP) to compare the two values character by character for hidden whitespace or a differing character set.
Kuehne+Nagel Rejected the Request
KUNA-EXTN-1001 - Error calling Kuehne+Nagel {operation}: {response body} (Http Code: {status})
Description: Kuehne+Nagel returned a failure response rather than shipment data. The message carries the operation that was attempted, the response Kuehne+Nagel sent back, and the HTTP status — shown by name rather than by number, so a 404 appears as NotFound and a 401 as Unauthorized. The most common causes are credentials that Kuehne+Nagel does not accept, an account whose API access has not been approved or has lapsed, and requests for a shipment the account is not entitled to see. Because the integration does not validate credentials when the subscription is saved, an incorrect Authentication_Id, Client_Code, or UserName first surfaces here rather than at setup.
Resolution: Check the status code and response text in the log entry. For a rejection that mentions authentication or authorization, re-check the three credential values on the Subscription Settings page against those issued by the Kuehne+Nagel Helpdesk, and confirm with the Helpdesk that API access is still active for your account. For a rejection that names the shipment, confirm the shipment exists and is visible to your Kuehne+Nagel account. If the credentials are confirmed correct and the rejection continues, contact your Managed Integration Service Provider (MiSP), or iPaaS.com Support at support@ipaas.com with the error timestamp, the shipment identifier, and the HTTP status code from the log entry.
Could Not Reach Kuehne+Nagel
KUNA-EXTN-1002 - The transport-level failure message returned by the failed connection, passed through unchanged — for example, "No such host is known." or "The operation has timed out."
Description: The request to Kuehne+Nagel could not be completed at all, so there is no response to report. This is a transport-level failure rather than a rejection: the address could not be resolved, the connection timed out, or the secure connection could not be established. The most common configuration cause is an API Url that is incorrect or points somewhere unreachable from iPaaS.com.
Resolution: Confirm the API Url on the Subscription Settings page is the address supplied by Kuehne+Nagel. If it is correct and the failure repeats, the Kuehne+Nagel API may be temporarily unavailable — retry the transfer later. If it continues past a short outage, ask your Managed Integration Service Provider (MiSP) to confirm the endpoint is still reachable from your environment.