Air cargo integration
Air Cargo EDI and API Integration
Airlines, forwarders and handlers each specify their own message versions and connection methods, so shipments are often re-keyed into carrier portals and status is chased by email. ECOM connects your forwarding, transportation, ERP and warehouse systems to the airlines, forwarders and agents you trade with, then maps, validates, tests and monitors bookings, air waybills, house waybills, status and billing messages.
Overview
What is air cargo EDI and API integration?
Air cargo EDI and API integration is the automated exchange of shipment data between forwarders, airlines, ground handlers, shippers and customs authorities. The core messages are the booking, the air waybill (AWB) and, for consolidations, the house waybill, followed by status messages and the freight invoice. IATA publishes the air cargo messaging standards: Cargo-XML, the current XML family (for example XFWB for the waybill and XFSU for status), and the older Cargo-IMP messages such as FWB and FSU that many partners still exchange. In the United States, shippers and forwarders also use ANSI X12 documents such as the 104 and 110, and airlines file security and manifest data with U.S. Customs and Border Protection. Which messages, versions and connection method apply is set by each partner.
Overview
Carrier, forwarder and handler roles stay distinct
Air cargo responsibilities are split between parties. Naming your role first keeps the integration scope clear.
Airlines and cargo carriers
You receive bookings, waybills and house data from forwarders, and send acknowledgments, status and invoices back.
Freight forwarders
You book space, send master and house waybill data to airlines and keep shippers informed from the airline’s status messages.
Ground handlers and handling partners
You report acceptance, handling and flight events that the airline and forwarder rely on.
Shippers
You need booking confirmation, status and billing information from your forwarder or airline in your own systems.
How ECOM helps
How ECOM supports air cargo workflows
ECOM’s role is the connection and coordination between your systems and your air cargo partners.
Shipment data entered once
Booking, waybill and house data flow from the system where the shipment is created, instead of being re-keyed into each airline portal or email.
Milestones you can see
Status messages such as freight on hand and ready for carriage reach your TMS or visibility tools, so you know when the airline has accepted the cargo.
Fewer rejected waybills
Messages are validated before they are sent, so errors are corrected on your side rather than returned by the airline as rejections close to the cutoff.
Invoices you can reconcile
Freight invoices that carry the air waybill reference can be matched to what was booked and tendered before they are paid.
How ECOM delivers it
Message mapping
Booking, waybill, house waybill, status and invoice data mapped between your systems and the format each partner specifies, whether Cargo-XML, Cargo-IMP, X12 or an API.
Validation before sending
Each outbound message is checked against the partner specification, and acknowledgments and rejections are matched back to the shipment they refer to.
Connectivity
Connections over AS2, SFTP, HTTPS and APIs, hosted by ECOM or opened to the partner, according to what each airline or agent supports.
Specification review and testing
ECOM reviews the partner specification, builds the maps, and tests scenarios with the partner, including corrections, rejections and consolidations, before go-live.
Monitoring and alerts
Missing acknowledgments, absent status messages and failed transfers surface as exceptions so someone can act before the shipment misses its flight.
Ongoing support
ECOM offers 24×7 support, with coverage hours and response targets defined in each service agreement.
ECOM offerings for this workflow
Systems Integrator
Connects TMS, ERP and WMS platforms (and the forwarding system you use) with the messages exchanged with airlines, handlers and forwarders. Hundreds of customers use the Systems Integrator today, and ECOM performs these integrations for customers.
Exception Management Center
Helps automate exception handling and manage internal and customer-facing SLAs, such as a booking not confirmed or a waybill not acknowledged.
Transaction Life Cycle Manager
Holds shipment paperwork and supporting evidence, including proof of delivery, signatures, damage reports and shortage reports.
Freight Onboarding
Brings carriers and other freight partners live.
Trading Partner Onboarding
A self-service portal that supports almost all verticals, with customer click-through onboarding, protocol-specific setup and automated transaction testing.
Reconcile360 (invoice-to-cash)
Invoice-to-cash automation across all verticals, including air partners, so freight billing connects to cash.
Which offerings apply, and the partners, protocols and systems in scope, are agreed with you during scoping.
Workflow
From booking to freight invoice: the air shipment lifecycle
A forwarder or shipper books space, prepares the air waybill, hands the cargo to the airline and follows it to the destination. Each stage produces data that other systems need. The messages named below are the ones the IATA e-AWB procedure and common U.S. practice use; your partners may differ.
- 01
Plan and book
The forwarder or shipper asks the airline for space and receives an answer. A confirmed booking carries the Booked (BKD) status.
Typical messages: Booking request (XFFR or FFR); booking answer (XFFR or FFA)
- 02
Prepare waybill and house data
The shipment record is created in the forwarder system. For consolidations the house waybill data is created as well, and security declaration data is carried where the screening process requires it.
Typical messages: Air waybill (XFWB or FWB); house waybill (XFZB) and house list (FHL or XFHL)
- 03
Airline acknowledgment
The airline checks the message and acknowledges it, or rejects it with the errors so the forwarder can correct and resend.
Typical messages: Response message (XFNM) with acknowledgment (FMA) or rejection (FNA)
- 04
Cargo acceptance
The airline or its handler receives the freight and reports it as on hand, then as ready for carriage once acceptance checks pass.
Typical messages: Status message (XFSU or FSU) with Freight on Hand (FOH) and Ready for Carriage (RCS)
- 05
Flight and in transit
The cargo is manifested, loaded and flown. Flight and status messages tell forwarders and handlers where it is.
Typical messages: Flight manifest (XFFM or FFM); status messages (XFSU or FSU)
- 06
Arrival and handoff
The destination handler receives the cargo and the consignee or forwarder is notified. This is where handoff gaps appear if data did not travel with the shipment.
Typical messages: Status messages (XFSU or FSU); X12 214 where a partner uses it
- 07
Customs and delivery
Customs and security filings are made as the airline and local rules require, then the cargo is released and delivered.
Typical messages: ACAS and air manifest filings with U.S. Customs and Border Protection; delivery status
- 08
Invoice and settlement
The airline or forwarder invoices the freight, and the payer audits the invoice against the booking and rate before paying.
Typical messages: X12 110 Air Freight Details and Invoice; X12 997 or 999 acknowledgments
Who sends which air cargo message to whom
Most air cargo messages travel between a forwarder and an airline, with handlers and customs authorities at the edges. The diagram shows the typical direction of each message; the tables that follow give the purpose, trigger, data and systems for each.
Illustrative example: one consolidated export shipment
An illustrative shipment, followed step by step. Partners define their own messages and sequence.
| Step | Message | From → to | What the integration checks |
|---|---|---|---|
| Book space | Booking request (XFFR) | Forwarder → airline | Required booking fields are present, and the booking reference is stored against the shipment. |
| Confirm booking | Booking answer (XFFR, status BKD) | Airline → forwarder | The answer matches the request, and the booked flight and weight are saved in the TMS. |
| Send waybill and house data | Waybill (XFWB) and house waybills (XFZB) | Forwarder → airline | House pieces and weights add up to the master waybill before sending. |
| Acknowledge or reject | Response (XFNM) | Airline → forwarder | The airline’s acknowledgment (FMA) closes this step; it is separate from acceptance of the cargo, which arrives later as status. A rejection (FNA) is shown with its errors, corrected and resent. |
| Accept the cargo | Status (XFSU: FOH, then RCS) | Airline or handler → forwarder | Both statuses arrive before the cutoff, or an alert is raised. |
| Invoice the freight | Air freight invoice (X12 110) | Airline → payer | The invoice carries the waybill number and is compared with the booked rate. |
Messages
Transactions and messages
Typical requirements—confirm with your trading partner.
Booking, air waybill and acknowledgment messages
These IATA messages carry the booking and the waybill from forwarder to airline, and the airline response back. The e-AWB procedure published by IATA prefers Cargo-XML and names the Cargo-IMP equivalents where the older format is still used.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| XFFR (FFR) Booking request IATA Cargo-XML, Cargo-IMP | Asks the airline to reserve space for a shipment. | Forwarder or shipper to Airline | Shipment planned and space needed on a flight | Origin and destination, pieces, weight, volume, commodity, requested flight or date | Forwarding system or TMS to airline reservation system | Bookings made from the system of record instead of portals and email |
| XFFR (FFA) Booking answer IATA Cargo-XML, Cargo-IMP | Tells the forwarder whether space is confirmed, with the Booked (BKD) status. | Airline to Forwarder or shipper | Airline decision on the booking request | Booking status, flight and date, confirmed pieces and weight | Airline reservation system to forwarding system or TMS | Confirmed space visible where planners work |
| XFWB (FWB) Air waybill (e-AWB data) IATA Cargo-XML, Cargo-IMP | Sends the master air waybill data electronically so the airline does not rely on paper. | Forwarder to Airline | Shipment prepared for export, before the cargo is tendered | Shipper and consignee, routing, pieces, weights, rates and charges, handling information, security data | Forwarding system, TMS or ERP to airline cargo system | One electronic waybill instead of re-keyed or paper documents |
| XFZB (FHL, XFHL) House waybill and house manifest data IATA Cargo-XML, Cargo-IMP | Gives the airline the house waybills behind a consolidated master waybill. | Forwarder to Airline | Consolidation built and master waybill ready | House waybill numbers, shippers and consignees, pieces and weights per house shipment | Forwarding system to airline cargo system | House and master data that agree before acceptance |
| XFNM (FMA, FNA) Response message: acknowledgment or rejection IATA Cargo-XML, Cargo-IMP | Confirms the airline received a message, or rejects it with errors so the sender can correct and resend. | Airline to Forwarder | Airline processes a waybill or house message | Reference to the message, accepted or rejected, error descriptions | Airline cargo system to forwarding system | Rejections caught and corrected before the cutoff |
Acceptance, status and flight messages
Status and flight messages tell forwarders and handlers where cargo is. The IATA procedure names Freight on Hand (FOH) and Ready for Carriage (RCS) as acceptance milestones; other milestone codes are defined in the IATA manuals and by each airline.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| XFSU (FSU) Status message IATA Cargo-XML, Cargo-IMP | Reports a milestone for a waybill, such as Freight on Hand or Ready for Carriage. | Airline or ground handler to Forwarder | Cargo received, accepted or moved | Waybill number, status code, date and time, station, pieces and weight | Airline or handler warehouse system to TMS or visibility tool | Milestones and acceptance visible without calling the airline |
| XFFM (FFM) Flight manifest IATA Cargo-XML, Cargo-IMP | Lists the cargo loaded on a flight. | Airline to Destination handler, customs or agreed party | Flight departure | Flight, waybills loaded, pieces and weights | Airline cargo system to handler or authority systems | Destination ready for what is arriving |
| XFBL Freight booked list IATA Cargo-XML | Lists the consignments for which space has been reserved on a particular flight. | Airline to Handler or agreed party | Before flight departure | Flight, booked consignments, pieces, weights | Airline cargo system to handler systems | Handlers prepare for the booked load |
| 214 Transportation Carrier Shipment Status Message ANSI X12 | Reports shipment events for partners that use X12 for status. | Carrier to Shipper, consignee, broker or 3PL | Pickup, transit, arrival or delivery event | Status and reason codes, date and time, location, shipment references | Carrier system to TMS or visibility tool | Consistent milestones across carriers |
X12 shipment and invoice documents, and U.S. customs filings
North American shippers and forwarders often use ANSI X12 for air shipment data and invoices, and airlines file advance data with U.S. Customs and Border Protection. Confirm with each partner which of these it uses.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| 104 Air Shipment Information ANSI X12 | Gives an air carrier the waybill and rating data for a shipment. | Shipper or air freight forwarder to Air carrier | Shipment ready to tender | Shipper, consignee, pieces, weights, dimensions, charges | ERP, TMS or forwarding system to carrier system | Waybill data sent without keying a paper air waybill |
| 110 Air Freight Details and Invoice ANSI X12 | Bills the customer for air transportation and related charges. | Air carrier or forwarder to Shipper or bill-to party | Shipment delivered or billing event | Air waybill reference, weight charges, surcharges, accessorials, totals | Carrier billing system to ERP or freight audit | Invoices matched to bookings and rates before payment |
| 997 / 999 Functional and implementation acknowledgments ANSI X12 | Acknowledges at the syntax (997) or implementation-guide (999) level whether an X12 file could be read. It is not the airline’s acceptance of a booking or waybill. | Receiver of the file to Sender of the file | Receipt of any X12 file | Accepted or rejected status and error detail | EDI translation and monitoring layer | Unreceived or rejected files noticed quickly |
| ACAS and air manifest Advance screening and manifest filings CBP ACE (AIR-CAMIR); ACAS messages | Provides pre-arrival air cargo data to U.S. Customs and Border Protection. CBP states ACAS is mandatory for airlines flying to the United States. | Airline, with forwarders supplying data as the airline requires to U.S. Customs and Border Protection | Before cargo is loaded or arrives, per CBP rules | Shipper and consignee, cargo description, piece count, weight, screening data | Airline and forwarder systems to CBP systems | Data ready early enough to avoid screening holds |
APIs and data-sharing options
Alongside messages, some partners offer APIs, and IATA is developing ONE Record, a data-sharing approach for air cargo. Availability and scope vary widely by partner.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| ONE Record Data-sharing standard for air cargo IATA ONE Record | Shares shipment data between parties through a common data model and API specification instead of point-to-point messages. IATA publishes mapping guidance between Cargo-XML and ONE Record. | Any participating party to Any participating party | Shipment data created or updated | Shipment and piece data in IATA’s ONE Record data model | Forwarder, airline and handler systems | A path from message exchange toward shared shipment data |
| Partner APIs Booking, rate and tracking APIs Partner-defined (typically REST over HTTPS) | Lets a system request or receive booking, rate or tracking data in real time where an airline or forwarding platform offers an API. | Your system or the partner to The partner or your system | A booking, quote or tracking request | Defined by the partner’s API specification | Forwarding system, TMS and partner platform | Real-time answers without portal work |
Cargo-XML, Cargo-IMP, X12 and APIs compared
A single air cargo project can involve several of these. This table shows how they typically differ; the airline or forwarder you connect with decides which one you use.
| Criteria | Cargo-XML | Cargo-IMP | ANSI X12 | APIs and ONE Record |
|---|---|---|---|---|
| What it is | IATA XML messages such as XFWB, XFZB, XFSU and XFNM | IATA text messages such as FWB, FHL, FSU and FFR | ANSI X12 transaction sets such as 104, 110 and 214 | Partner REST-style APIs, and IATA ONE Record data sharing |
| Typical use | Waybill, house waybill, status and booking exchange with airlines and agents | Legacy exchange with partners that have not moved to XML | Shipper and forwarder air shipment data and invoices in North America | Booking, rates, tracking and data sharing where a partner offers it |
| Who sets the rules | IATA, then each airline | IATA, then each airline | ASC X12, then each trading partner | The partner, or IATA for ONE Record |
| What to confirm | Message versions and status codes | Message versions and sequence | Version, segments and acknowledgments | Authentication, endpoints and limits |
Systems
How the integration fits between your systems and your air cargo partners
The architecture is the same for a forwarder, a shipper or an airline: your systems create and consume the data, and the integration layer maps it, validates it, connects it to each partner and watches it. The diagram is illustrative; scope is confirmed from your requirements.
Systems an air cargo integration connects
Air cargo data starts in several systems and ends in several more. Integration scope usually covers the ones below, and the right mix depends on whether you are a forwarder, a shipper or an airline.
| System | What flows | What to plan for |
|---|---|---|
| Forwarding system or TMS | Bookings, air waybill and house waybill data, status updates and freight charges. | The system of record for the shipment; its references must reach every message and invoice unchanged. |
| ERP and accounting | Shipment references from orders, freight accruals, airline invoices and payments. | Invoices are audited against booked rates and shipment data before payment. |
| WMS and handling systems | Freight on hand, cargo acceptance and warehouse milestones. | Event timing and time zones matter when partners measure acceptance against cutoffs. |
| Airline and handler systems | Booking answers, acknowledgments, rejections, flight and status messages. | Each airline defines its own versions, codes and connection method. |
| Customs and security filings | Advance screening and manifest data filed with U.S. Customs and Border Protection. | Filing responsibility, timing and message layout come from CBP and the airline. |
Problems and exceptions
Air cargo integration problems and how ECOM addresses them
These are the problems that most often bring air cargo teams to integration.
| Problem | Why it hurts | How ECOM addresses it |
|---|---|---|
| Manual shipment entry and disconnected systems | Bookings and waybills are re-keyed into airline portals or emailed, so errors creep in and the forwarding system, TMS and ERP disagree. | Mapping from your system of record to each partner format, with connectivity over the protocol the partner supports, so data is entered once. |
| Missing milestones | Without freight-on-hand, ready-for-carriage and flight status, teams phone the airline to find out whether the cargo was accepted. | Status messages mapped to consistent milestones in your TMS or visibility tools, with monitoring that flags shipments that have no expected status. |
| Rejected waybills and house data | A rejection close to the cutoff can mean the cargo misses its flight, and the cause is often a version or data mismatch. | Validation against the partner specification before sending, rejection messages matched to the shipment, and scenario testing of corrections before go-live. |
| Air shipment handoff gaps | Data that does not travel with the cargo to the handler and destination leaves consignees and customs partners without what they need on arrival. | References carried unchanged from booking to waybill to status and invoice, with monitoring of the messages that should reach each party. |
| Freight invoice discrepancies | Invoices that do not match the booking, rate or waybill are disputed by hand and paid late. | Invoice data mapped to your ERP with the waybill reference intact, so invoices can be compared with bookings and shipments. |
| Slow airline and partner onboarding | Each airline has its own specification, versions and test process, so new connections take longer than the business wants. | Specification review, reusable maps, partner test scenarios and tracking of each partner through to production, followed by monitoring and 24×7 support. |
Handling air cargo exceptions before they become delays
Exceptions are normal in air cargo. What matters is that they are detected, routed to someone and corrected with the original shipment reference attached.
| Exception | Typical cause | How it is handled |
|---|---|---|
| No acknowledgment received | Connection failure, an unprocessed file or a message sent to the wrong endpoint. | A missing-response alert after the agreed interval, with the transfer history available for diagnosis. |
| House data does not match the master waybill | Consolidation changes that updated one message but not the other. | Checks on piece and weight totals between house and master data before the messages are sent. |
| Customs or screening action message | CBP or the airline requests more information or holds the cargo. | The action message is routed to the responsible team with the shipment reference so the response is timely. |
Get started
How an air cargo integration project works with ECOM
Every airline, handler and forwarder specifies its own requirements, so the work starts with your partner and the problem you are solving.
- 01
Tell us the partner, systems and problem
Use the contact form or call, and describe who you need to connect with, what you run and what is going wrong.
- 02
Review the specification
An ECOM specialist reviews the airline or partner specification: messages, versions, codes, connection method and test process.
- 03
Agree scope and approach
We outline the messages, mapping, connections and testing involved, and how delivery would work, so you can compare options.
- 04
Build and test with the partner
Maps and connections are built, then tested with the partner using realistic scenarios such as consolidations, corrections and rejections.
- 05
Go live and monitor
Production starts with monitoring in place, and 24×7 support is available with coverage defined in your service agreement.
Helpful to share, never required
- The airline, forwarder or handler you need to connect with
- The partner specification or onboarding document, if you have one
- Your current systems, for example forwarding system, TMS, ERP and WMS
- The messages you need, for example booking, waybill, house waybill, status or invoice
- The business problem you want to solve
- Your target timeline
Have a carrier specification? Send it for review Call Sales: 972-836-7750
Sources
Sources and related pages
Standards and partner requirements are revised over time, and each trading partner publishes its own. Confirm current versions with the partner before you build.
Standards and public sources
- IATA Cargo-XML ToolkitIATA’s description of Cargo-XML, the Cargo-IMP manual and ONE Record mapping guidance.
- IATA Cargo-XML messages listMessage names and acronyms (XFWB, XFZB, XFHL, XFFM, XFBL, XFSU, XFNM, XFFR and others); document dated November 2018.
- IATA e-AWB Standard Operating ProcedureRoles and messages between forwarder, airline and handler, including acknowledgments, rejections and status.
- IATA ONE Record specificationMapping between Cargo-XML messages and ONE Record, with links to the data model and API specification.
- U.S. CBP: Air Cargo Advance Screening (ACAS)Program description and mandatory status for airlines flying to the United States.
- U.S. CBP: ACAS FAQsData elements and the messages airlines and forwarders exchange with CBP.
- ASC X12 transaction setsOfficial names of the 104, 110 and 214 transaction sets.
Related pages
- EDI 104 Air Shipment InformationThe X12 shipment document in detail.
- EDI 110 Air Freight Details and InvoiceThe X12 air freight invoice in detail.
- EDI 214 Shipment Status MessageStatus messages and code mapping.
- Transportation and logistics EDIAll modes: truck, rail, ocean and air.
- Rail freight EDI and API integrationRailroad documents, interchange and equipment visibility.
- Ocean freight EDI and API integrationBooking, shipping instructions, VGM and container tracking.
- Carrier trading partner guidesIntegration guides for carriers.
- Logistics trading partner guidesIntegration guides for logistics providers.
- Trading partner onboardingHow certification and onboarding run.
- Carriers & Freight TransportationRoad, rail, ocean, air, intermodal and cross-border freight: freight onboarding, systems connectivity, exceptions and delivery evidence.
- Logistics AutomationAutomate tenders, status updates, freight invoices and warehouse orders with logistics partners.
- Supply Chain VisibilityTrack orders, shipments and invoices across partners and catch exceptions early.
- API IntegrationConnect partner and application APIs to your systems and bridge them with EDI processes.
FAQs
Frequently asked questions
What is air cargo EDI?
Air cargo EDI is the exchange of structured shipment messages between forwarders, airlines, handlers and shippers, such as bookings, air waybills, status updates and invoices. IATA defines the air cargo messages, and X12 documents such as the 104 and 110 are also used in North America.
What is the difference between Cargo-IMP and Cargo-XML?
Both are IATA messaging standards. Cargo-IMP messages such as FWB and FSU are compact text messages, while Cargo-XML messages such as XFWB and XFSU carry the same business data in XML. IATA prefers Cargo-XML for new work, but many partners still exchange Cargo-IMP, so confirm what each airline accepts.
What are the FWB and XFWB messages?
The FWB is the Cargo-IMP air waybill message, and the XFWB is its Cargo-XML equivalent. In the IATA e-AWB procedure the forwarder sends it to the airline with the shipment data, and the airline replies with an acknowledgment or a rejection.
What does the airline send back after a waybill message?
In the IATA e-AWB procedure the airline acknowledges the message, or rejects it with an error response so the forwarder can correct and resend. Status messages such as freight on hand and ready for carriage follow as the cargo is accepted.
What is ACAS and does it affect my integration?
Air Cargo Advance Screening (ACAS) is a U.S. Customs and Border Protection program under which airlines submit pre-arrival data before cargo is loaded; CBP states the requirements are mandatory for airlines flying to the United States. Forwarders may exchange ACAS data with airlines, so your airline partner will tell you what it needs from you and when.
Which X12 documents are used for air freight?
The X12 104 Air Shipment Information carries shipment details to an air carrier, the 110 Air Freight Details and Invoice bills the freight, and the 214 reports shipment status. The 997 or 999 acknowledges each X12 file at the syntax or implementation level; it does not by itself show that the airline accepted the shipment.
Can ECOM connect to an airline that only offers an API?
ECOM reviews each partner specification and connects over the protocol or API the partner supports. Whether a particular airline interface is in scope is confirmed when your requirements are reviewed, so send us the specification if you have it.
What should I send ECOM to get started?
The airline or forwarder you need to connect with, your current systems, the messages you need, the business problem and your target timeline. A specification is helpful but not required to begin the conversation.
Discuss the air cargo messages you need to send or receive
Tell us the airline or forwarder, your systems and the problem you are trying to solve. An ECOM specialist will review the messages, versions and testing involved.