Amadeus Quick Connect (AQC) Flight Orders Commission

In the current airline distribution environment, declaring commission is no longer a passive back-office process - it is an essential step in the ticketing process. For travel OTAs, agencies, CTOs, and GDS integrators using the Amadeus Quick Connect API, commission data management can have a direct impact on the success of ticket issuance.

The Flight Orders Commission (FM Element) API in Amadeus Quick Connect (AQC) allows agencies to make a clear declaration of commission responsibility for an existing flight order. Although this API does not impact pricing or availability, it is an essential step in ensuring that the booking is commercially compliant, audit-ready, and ticketable.

If you are developing or optimizing a Flight booking API for OTA platforms using GDS API integration, this step is critical for a production-ready solution.

The Flight Orders Commission API is designed to attach commission information to an already confirmed flight order within the Amadeus AQC API integration flow.

Its primary purpose is to create the FM Element in the underlying PNR structure.

Core objectives

This API is used to:

• Declare agency commission responsibility
• Store commission details in the flight order
• Ensure ticketing compliance in regulated markets
• Support manual commission environments
• Fulfill airline and IATA requirements

Important clarification

The API does NOT:

• Reprice the booking
• Change availability
• Modify itinerary data

It is purely a commercial declaration layer.

Why the FM Element matters

In many markets:

• Airlines require an explicit commission declaration
• Zero commission must still be recorded
• A missing FM element may cause ticketing failure
• Audit trails depend on this data

For serious Amadeus flight booking API implementations, skipping this step can lead to downstream operational issues

Within the broader Amadeus Quick Connect API booking lifecycle, the commission step occurs after order creation but before ticketing.

High-level workflow

1. User searches flights
2. System prices the selected offer
3. Flight order is created
4. Agency evaluates commission requirements
5. Commission API is called
6. FM Element is stored in PNR
7. Ticketing proceeds safely

Technical behavior

The API works as a PATCH operation on the flight order resource.

Key characteristics:

• Order-level update
• No session required
• OAuth-secured
• Immediate persistence in PNR
• Idempotent business intent (but avoid blind retries)

Authentication requirement

Like all protected endpoints, this call requires Amadeus OAuth2 authentication using the AQC access token.

Below is a simplified version focusing only on the most important parameters for developers working on GDS API integration.

Sample Request

Copy
1{
2 "data": {
3   "type": "flight-order",
4   "id": "eJzMPM3MzcCAArNAiI",
5   "commissions": [
6     {
7       "controls": ["MANUAL"],
8       "values": [
9         {
10           "commissionType": "NEW",
11           "percentage": "0"
12         }
13       ]
14     }
15   ]
16 }
17}

Key parameters

controls: MANUAL

• Mandatory in AQC
• Confirms the agency takes responsibility
• No automatic calculation

commissionType: NEW

• Only supported value
• Creates the FM element

percentage

• Commission percentage
• “0” is valid and often required
• Must be validated client-side

Sample Response

Copy
1{
2 "data": {
3   "id": "eJzTMPM3MzcCAArNAiI",
4   "commissions": [
5     {
6       "controls": ["MANUAL"],
7       "values": [
8         {
9           "commissionType": "NEW",
10           "percentage": 0
11         }
12       ]
13     }
14   ]
15 }
16}
17

What the response confirms

• Flight order still valid
• FM element successfully stored
• No pricing changes occurred
• Order is ready for ticketing

For production Amadeus AQC API integration, always persist the full response.

Even experienced teams building Flight booking API for OTA platforms encounter issues with the commission step.

1. Calling the API at the wrong stage

Problem: Commission attempted before order creation
Impact: Hard failure

Best practice:
Only call after a successful Flight Order Create.

2. Missing MANUAL control

Problem: Omitting the controls field
Impact: Validation error (400)

Reality:
AQC currently supports only MANUAL.

3. Invalid commission values

Common mistakes:

• Negative percentage
• Wrong data type
• Unsupported format

Mitigation:

• Always validate client-side
• Enforce numeric bounds
• Normalize decimals

4. Order state conflicts

You cannot apply commission if the order is:

• Cancelled
• Fully flown
• Already ticketed
• Closed

Recommended approach:

Implement pre-validation using Flight Order Get.

When implemented correctly, the Amadeus AQC API integration for commission handling delivers strong operational and commercial advantages.

Compliance readiness

• Meets airline requirements
• Supports IATA-driven markets
• Prevents ticketing rejection
• Improves audit posture

Operational reliability

• Reduces ticketing failures
• Standardizes commission workflow
• Improves back-office reconciliation
• Enables predictable automation

Commercial transparency

• Explicit commission declaration
• Better partner reporting
• Cleaner financial audits
• Supports multi-market operations

Scalability for OTAs

For growing OTA platforms using GDS API integration, this API enables:

• Multi-airline compatibility
• Market-specific logic
• Flexible commission models

Enterprise-grade booking flows

The Flight Orders Commission (FM Element) API may seem like a small part of the overall Amadeus Quick Connect API world, but its value is out of proportion.

For travel OTAs, agencies, and marketplaces, this step is critical to ensure that flight orders are valid, safe, and ticketable. Failure to address the commission declaration can result in ticketing errors, audit problems, and airline rejections.

A good Amadeus AQC API integration strategy must consider the commission step as a first-class citizen in the booking flow, not an afterthought.

Doing it right makes the FM Element a silent but mighty facilitator of trustworthy airline distribution.

Ready to Accelerate Your Amadeus Integration?

Planning to integrate Amadeus Quick Connect (AQC) APIs into your travel platform? Our experienced Amadeus API integration experts help you implement secure authentication, flight search, pricing, booking and ticketing workflows end to end. Contact us today to accelerate your Amadeus integration.