Portal Info

Kuehne+Nagel LTL Plus accounts are administered through the LTL Plus portal:

https://my.ltlp.kuehne-nagel.com

API access is not enabled by default. It is requested from the Kuehne+Nagel Helpdesk, which issues the Authentication ID and Client Code the integration sends on every call — see the Kuehne+Nagel Installation Instructions.

API Endpoints Intro

The Kuehne+Nagel LTL Plus shipment-tracking API is a REST API that accepts and returns JSON. Every call the integration makes is a POST, including the two read operations below — the search criteria travel in the request body rather than the query string.

The base URL is the value entered in the API Url subscription setting. For production:

https://api.ltlp.kuehne-nagel.com/api

Throughout this article, [Base URL] stands in for that value.

Kuehne+Nagel does not publish a versioned public specification for this service, so there is no version segment in the paths and no separate sandbox host. Endpoint details are supplied by Kuehne+Nagel directly when API access is granted.

Shipment Endpoints
Authentication
Pagination
Rate Limits and Concurrency
Authorization Endpoint

Shipment Endpoints

Get Shipments (POST)

[Base URL]/ShipmentTracking/ShipmentStatusDetail

Retrieves the current details for a single shipment. Used when a shipment is transferred individually — from the iPaaS.com Manual Sync page, and for each shipment identified by a polling run.

Request body:

Field	Description
`Username`	The Kuehne+Nagel website user ID from the subscription settings.
`ClientCode`	The client code issued by the Kuehne+Nagel Helpdesk.
`AuthenticationID`	The authentication identifier issued by the Kuehne+Nagel Helpdesk.
`carrierCode`	The carrier SCAC code — the second half of the shipment identifier.
`searchValue`	The value to search for — the Bill of Lading number.
`searchType`	The kind of value being searched. The integration always sends `BL`, so shipments are looked up by Bill of Lading number.

The response carries an error message field and a list of shipment detail records. The integration uses the first record returned.

Poll Shipments (POST)

[Base URL]/ShipmentTracking/ShipmentStatusList

Retrieves every shipment updated within a date range. Used by the scheduled shipment/poll event to find shipments that have changed since the previous run.

Request body:

Field	Description
`Username`	The Kuehne+Nagel website user ID from the subscription settings.
`ClientCode`	The client code issued by the Kuehne+Nagel Helpdesk.
`AuthenticationID`	The authentication identifier issued by the Kuehne+Nagel Helpdesk.
`startDate`	The beginning of the search window. The integration uses the point the previous successful poll completed, moved further back when a look-back value is set on the polling event.
`endDate`	The end of the search window. The integration sends the maximum date value, so the window is open-ended.

The response carries the same shape as the single-shipment call. The integration reduces it to the Bill of Lading number and SCAC code of each shipment, removes duplicates, and transfers each one individually.

Authentication

Kuehne+Nagel authenticates each request from three values sent in the request body: UserName, Client_Code, and Authentication_Id, all entered in the subscription settings. There is no authorization header, no token to obtain, and no token to refresh.

Because the credentials are checked only when a request is actually made, entering them does not by itself confirm they are correct — a rejection surfaces on the first transfer. See Kuehne+Nagel Connections and Settings for where each value is entered and how to rotate it.

Pagination

Neither endpoint is paginated. The single-shipment call returns the detail records for one shipment, and the polling call returns every shipment matching the date range in a single response.

Because the polling response is not paged, the size of each run is governed by how wide the date window is. Keeping the polling schedule regular keeps each response small; a long gap between runs, or a large look-back value, produces a correspondingly larger response.

Rate Limits and Concurrency

Kuehne+Nagel does not publish call limits for this API. Request volume is therefore governed by the subscription settings rather than by a documented quota:

Setting	Purpose
API Throttle Limit	Maximum number of calls made to Kuehne+Nagel within each throttle window.
API Throttle Seconds	Length of each throttle window, in seconds.
Concurrent Connections	Maximum number of simultaneous connections to Kuehne+Nagel.

Reduce these values if you encounter rate-limit errors, and stagger large catch-up polling runs rather than running them alongside other intensive processes.

Authorization Endpoint

There is no separate authorization endpoint. Kuehne+Nagel does not use an OAuth or token-exchange flow for this API — the credentials are sent with each request, as described under Authentication.

Kuehne+Nagel API Endpoints