IATA_Acknowledgement
Message · Acknowledgement · Implemented
Implemented
Delivers: .
The generic acknowledgement / error envelope returned across the API.
When to use
Sent to acknowledge receipt, or to report errors and warnings when a typed response is not applicable. Notification (push) messages are typically answered with an Acknowledgement.
Transport
| Property | Value |
|---|---|
| Method & path | POST /24.4/Acknowledgement |
| Content-Type | application/xml |
| Auth | Authorization: Bearer <token> (or X-API-Key: <key>) |
| Routing header | IATA-Message-Name: IATA_Acknowledgement |
See Authentication & connection for the full handshake.
Request example
note
✅ The example below validates against the original XSD.
<?xml version="1.0" encoding="UTF-8"?>
<IATA_Acknowledgement xmlns="http://www.iata.org/IATA/2015/EASD/00/IATA_OffersAndOrdersMessage"/>
Key fields
Top-level content model of IATA_Acknowledgement (one level deep, including inherited content):
| Field | Type | Required | Repeatable | Notes |
|---|---|---|---|---|
DistributionChain | DistributionChainType | — | — | |
Notification | AckType | — | — | |
PayloadAttributes | IATA_PayloadStandardAttributesType | — | — |
Build it with the SDK
The @oms/ndc-24-4 package is a reference SDK — build, serialize, parse, and validate this message in code:
import { IATA_Acknowledgement } from '@oms/ndc-24-4';
const xml = IATA_Acknowledgement.toXML(payload, { pretty: true });
const obj = IATA_Acknowledgement.parseXML(xml); // round-trips
IATA_Acknowledgement.schema.parse(obj); // strict Zod validation
Related
- All Acknowledgement messages
- Postman collection & SDK · OpenAPI contract