How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Kuehne+Nagel

Kuehne+Nagel Purchase Order Layer API

The purchase-order-layer API from Kuehne+Nagel — 3 operation(s) for purchase-order-layer.

Documentation Provider Profile APIs.io OpenAPI GitHub

Kuehne+Nagel Purchase Order Layer API is one of 48 APIs that Kuehne+Nagel publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include purchase-order-layer. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 3 paths, and defines 38 schemas. It is described by OpenAPI 3.2.0, at version v3.

Requests are made against a single base URL, https://internal.api.kuehne-nagel.com/order-management/purchase-order/v3.

4 operations 3 paths 38 schemas 1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Base URL
https://gateway.api.kuehne-nagel.com/track-trace/shipment/v2
Authentication
OAuth 2.0, API Key
Contact
Kuehne+Nagel ESP Public APIs
Resource Areas
1

Authentication & Security 2

Kuehne+Nagel Purchase Order Layer API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (default) using the implicit flow. An API key is passed in the header as apikey (api_key). By default, every request must be authenticated.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

purchase-order-layer 4
POST
/customers/{customerCode}/purchase-orders
Used by customers to create new purchase orders in ESP.
createPurchaseOrders 1 param body → 201202default
PATCH
/customers/{customerCode}/purchase-orders
Used by customers to update existing purchase orders.
updatePurchaseOrders 1 param body → 200202default
POST
/customers/{customerCode}/purchase-orders-search
Used by business parties linked to a purchase order to read one or more existing purchase orders.
readPurchaseOrders 1 param body → 207default
PUT
/customers/{customerCode}/purchase-orders-cancellations
Used by customers to cancel all or only a selection of order lines from one or more purchase orders.
cancelPurchaseOrderLines 1 param body → 200202default

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are OrderIdentificationKeyAttributes (33 properties), ItemIdentificationAttributes (17 properties), OrderAttributes (16 properties), ItemAttributes (9 properties). Each schema is shown below with its type and property counts.

ReadPurchaseOrdersRequest
object
1 property 1 required
OrderLineRequest
object
2 properties
Money
object
2 properties 1 required
ItemIdentificationAttributes
object
17 properties
Cancellation
object
2 properties 1 required
AmountAndUnit
object
2 properties 1 required
BulkReadResponse
object
2 properties
UpdatePurchaseOrdersRequest
object
1 property 1 required
Incoterms
string
Internationally recognized delivery terms for commercial contracts published by the ICC Possible values: CFR, CIF, CIP, CPT, CTO, DAF, DAP, DAT, DCT, DDP, DDU,…
CustomerCode
string
Unique identifier assigned to a customer
ResponsePurchaseOrder
object
4 properties 1 required
DateWindow
object
2 properties
Problem
object
5 properties 2 required
Integer
integer
CountryCode
string
OrderLineResponse
RequestPurchaseOrder
object
4 properties 1 required
OrderIdentificationKeyAttributes
object
33 properties
String
string
PostalAddress
object
5 properties
PurchaseOrderResponse
object
2 properties 1 required
ContactInformation
object
5 properties
Address
AdditionalReferencesRequest
object
2 properties
Date
string
Parties
object
4 properties
CreatePurchaseOrdersRequest
object
1 property 1 required
ItemAttributes
object
9 properties
Incompleteness
object
7 properties 4 required
CancelPurchaseOrderLinesRequest
object
1 property 1 required
BusinessParty
UnLocationCode
string
Standardized code for trade and transport locations including seaports and airports
OrderAttributes
object
16 properties
AdditionalParty
object
3 properties
CancelPurchaseOrderLinesResponse
object
1 property
OrderHeaderRequest
object
2 properties
KeyAttributes
object
3 properties
AdditionalReferencesResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kuehne-nagel-purchase-order-layer-api-openapi.yml Raw ↑

Other APIs Kuehne+Nagel publishes across the network.

Kuehne+Nagel Administration Layer API
AE Profile APIs.io
Kuehne+Nagel API Keys API
AE Profile APIs.io
Kuehne+Nagel Assigned Consignments API
AE Profile APIs.io
Kuehne+Nagel Background Tasks API
AE Profile APIs.io
Kuehne+Nagel Booking API
AE Profile APIs.io
Kuehne+Nagel Booking Requests API
AE Profile APIs.io
Kuehne+Nagel Cargo Items API
AE Profile APIs.io
Kuehne+Nagel Config API
AE Profile APIs.io
Kuehne+Nagel Container API
AE Profile APIs.io
Kuehne+Nagel Delete API
AE Profile APIs.io
Kuehne+Nagel Document API
AE Profile APIs.io
Kuehne+Nagel Document Request API
AE Profile APIs.io
#purchase-order-layer
← Back to K APIs
API Details
ID
kuehne-nagel:kuehne-nagel-purchase-order-layer-api
Base URL
https://gateway.api.kuehne-nagel.com/track-trace/shipment/v2
Docs
https://portal.api.kuehne-nagel.com/devportal/apis/6b98ae4c-ef06-4f72-acba-616584ee7f0f/overview
Provider
Kuehne+Nagel
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=kuehne-nagel-purchase-order-layer-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/kuehne-nagel-purchase-order-layer-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Kuehne+Nagel Purchase Order Layer API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.