...
Only Aggregators and IATA Travel Agents that are registered and certified with Iberia’s NDC API are eligible to use this functionality.
Both the Aggregator and Travel Agent and must have signed an addendum to our Terms & Conditions taking responsibility for data protection and fraud control prior to implementation. This will be part of the certification process.
Please open a service desk here (put link) to request access to use this functionality.
Delegation between different Aggregators is not permitted. The servicing of an Order can only be undertaken using the same Aggregator participant that was used for its creation.
Cross-border IATA Delegation is not supported. All Travel Agents, both Servicing and Responsible must be in the same country.
For Corporate Fares/Products, a valid relationship must be in place, in the Iberia Sales Database, between all the Travel Agents (IATA’s) involved and the Corporate entity
For Private Leisure Fare products, all Travel Agents (IATA’s) involved must have access to the same private fare products
The IATA used to issue documents is checked and reported to the BSP NDC Risk Management APIs.
The Travel Agent who’s IATA is used to issue all documents (the Responsible_IATA) is responsible for any and all settlement.
Any and all additional documents (re-issues, EMDs, etc.) will be issued and reported to BSP/ARC using the Responsible_IATA’s credentials.
If a change results in a Split, the new Order will maintain the Responsible_IATA of the original Order.
All confirmation emails will be sent to the Travel Agents email stored in the Order.
OrderList API is excluded from this functionality.
The OrderID must be used, and not the 5/6 digit BookingReference, in messages when this functionality is being used.
...