Kuehne + Nagel LTL+
  1. Overview
Kuehne + Nagel LTL+
  • Overview
    • Introduction
    • Acceptable Use Policy
    • Getting Started
    • Full Integration API Workflow
    • Support & Feedback
  • Accessorials
    • Accessorial - Retrieve all accessorial charge codes
      GET
  • BillOfLading
    • BOL - Create a bill of lading PDF
      POST
  • Quoting
    • RateQuote - Submit a quote request
      POST
    • RateQuote - Submit a quote request for multiple points
      POST
  • Document Retrieval
    • GetImageList - Retrieve list of available shipment documents
      POST
    • GetImage - Retrieve shipping documents based on DocumentID
      POST
  • Invoice
    • Invoice - Retrieve a single invoice or pull an entire week of invoices
      POST
  • Shipment Tracking
    • HTML Tracking Link Generation
    • TrackingList - Get a list of shipment tracking information
      POST
    • TrackingDetails - Retrieve all the tracking details related to a shipment
      POST
  • Load Tendering
    • LoadTender - Tender a shipment
      POST
    • LoadTender - Tender a shipment
      POST
  • Transit
    • Transit - Receive transit time for a shipment lane.
      POST
  • Orders
    • Order
      POST
    • OrderDetails
      POST
  1. Overview

Getting Started

Base URL#

Production: https://api.ltlp.kuehne-nagel.com/api
Development: 404 🙃
Production vs Development
The only endpoint that needs precaution is the Load Tendering endpoint. There is a developerMode boolean that needs to be set to true for testing.

Authorization#

You must provide the following information to our helpdesk at helpdesk@ec.kuehne-nagel.com to request an AuthenticationID for your organization. The AuthenticationID is used in most POST endpoints.
Third Party Developers
Provide the name of your company in addition to the customers name if you are developing this connection on behalf of a Kuehne + Nagel, LTL+ customer. If you are reaching out to us on behalf of the customer, we require our NDA to be executed.
Customer Name:
Contact Name:
Phone Number:
Email Address:

User-Agent Header Requirement#

To ensure proper identification and tracking of API usage, all API calls must include the User-Agent header. This header allows us to understand the context of the requests being made and can assist in troubleshooting and optimizing our services.

How to Include the User-Agent Header#

When making API requests, include the User-Agent header in your HTTP headers. Here’s an example of how to set the User-Agent header:
Example in cURL:

Important Notes#

Value Format: The value for the User-Agent header should typically include your application name and version (e.g., YourAppName/1.0).
Mandatory: This header is mandatory for all API requests. Requests without the User-Agent header may be rejected or logged for further investigation.
Previous
Acceptable Use Policy
Next
Full Integration API Workflow
Built with