IATA_ServiceDeliveryNotifRQ

Notification · Servicing & Delivery · Implemented

Implemented

This airline sends IATA_ServiceDeliveryNotifRQ to your notification endpoint — see Notifications. Delivers: ORDDEL Fulfilment notification (no tickets / EMDs) · ORDST2 Fulfilment notification to seller.

Limits today:

• ORDDEL — A service delivered with no ticket or EMD behind it is notified on its own: a seat sold for nothing when its flight flies, a partner (marketplace) product when its partner fulfils it (the marketplace's own fulfilment, delivered by the partner, read back every few minutes). Arcube connector offers are not sold over NDC (SHPAN3), so there is no fulfilment of theirs to notify.

Rests on simulated supply (operations) — flagged on every response; see Simulated supply.

Notification of a service-delivery event.

When to use

Push channel — reports that a service was delivered or consumed.

Transport

Property	Value
Method & path	POST /24.4/ServiceDeliveryNotifRQ
Content-Type	application/xml
Auth	Authorization: Bearer <token> (or X-API-Key: <key>)
Routing header	IATA-Message-Name: IATA_ServiceDeliveryNotifRQ

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_ServiceDeliveryNotifRQ xmlns="http://www.iata.org/IATA/2015/EASD/00/IATA_OffersAndOrdersMessage">
  <DistributionChain>
    <DistributionChainLink xmlns="http://www.iata.org/IATA/2015/EASD/00/IATA_OffersAndOrdersCommonTypes">
      <Ordinal>1</Ordinal>
      <OrgRole>Carrier</OrgRole>
      <ParticipatingOrg>
        <OrgID>X</OrgID>
      </ParticipatingOrg>
    </DistributionChainLink>
  </DistributionChain>
  <Request>
    <Order xmlns="http://www.iata.org/IATA/2015/EASD/00/IATA_OffersAndOrdersCommonTypes">
      <OrderID>X</OrderID>
      <OrderItem>
        <OrderItemID>X</OrderItemID>
        <OwnerCode>X</OwnerCode>
        <Service>
          <DeliveryProvider>
            <ID>X</ID>
            <Name>X</Name>
          </DeliveryProvider>
          <OrderServiceAssociation>
            <PaxSegmentRef>
              <PaxSegmentRefID>X</PaxSegmentRefID>
            </PaxSegmentRef>
          </OrderServiceAssociation>
          <PaxRefID>X</PaxRefID>
          <ServiceID>X</ServiceID>
        </Service>
      </OrderItem>
      <OwnerCode>X</OwnerCode>
    </Order>
  </Request>
</IATA_ServiceDeliveryNotifRQ>

Key fields

Top-level content model of IATA_ServiceDeliveryNotifRQ (one level deep, including inherited content):

Field	Type	Required	Repeatable	Notes
AugmentationPoint	xs:any	—	—	extension point (AugmentationPoint)
DistributionChain	DistributionChainType	✓	—
PayloadAttributes	IATA_PayloadStandardAttributesType	—	—
Request	ServiceDeliveryNotifRequestType	✓	—

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_ServiceDeliveryNotifRQ } from '@oms/ndc-24-4';

const xml = IATA_ServiceDeliveryNotifRQ.toXML(payload, { pretty: true });
const obj = IATA_ServiceDeliveryNotifRQ.parseXML(xml);    // round-trips
IATA_ServiceDeliveryNotifRQ.schema.parse(obj);            // strict Zod validation

Related

• All Servicing & Delivery messages
• Postman collection & SDK · OpenAPI contract