Europe · Developers
Travel API integration for European engineering teams
European engineering teams integrating flight and hotel content face more than an API schema. NDC changes how offers are priced and serviced, strong customer authentication shapes the checkout, and GDPR governs every passenger name you store. Avunzo, Voraal's unified travel API, is designed so those concerns are handled in the right layer.
Built for
- OTAs and metasearch-driven retailers
- Corporate booking tool builders
- Banks and loyalty programmes
- Travel startups
- TMC in-house tech teams
In brief
What should a European team plan for when integrating a travel API?
Plan for three layers: content (GDS, NDC and low-cost carrier offers with different servicing rules), payments (strong customer authentication on most EEA card payments, handled by your payment provider) and data (GDPR roles, a processing agreement and a lawful transfer route). Voraal's Avunzo API normalises the content layer and supports sandbox testing, webhooks and idempotent bookings.
By the Voraal team · Updated
Why NDC is the first design decision in Europe
Several large European airline groups have pushed agencies towards NDC by adding a surcharge to tickets issued through traditional GDS channels while exempting NDC and direct bookings. Lufthansa Group's distribution cost charge and Air France-KLM's GDS surcharge are the best-known examples; the amounts change, so check the current figures with each carrier. For a European retailer, this turns NDC from a technical upgrade into a pricing question.
NDC offers are not just fares in a new format. They carry bundles, ancillaries and servicing rules that differ by airline, and post-booking changes go through order-style calls rather than classic PNR edits. Our NDC integration page explains how Voraal handles this, and the GDS vs NDC guide sets out when each channel makes sense. Avunzo returns GDS, NDC and low-cost carrier results in one schema, so your front end compares like with like.
Payments: where strong customer authentication sits
Under PSD2, most customer-initiated card payments in the European Economic Area must use strong customer authentication, usually through 3-D Secure. Exemptions exist for low-value payments, low-risk transactions approved through transaction risk analysis, and merchant-initiated transactions such as charging a saved card after the customer has left checkout. The EU's PSD3 and Payment Services Regulation texts were agreed in 2026 and refine these rules, but they apply only after formal adoption and a transition period.
In an Avunzo integration, card authentication is performed by your payment service provider, not by the travel API. The booking call should only run after payment authorisation succeeds, and the idempotency key on the booking request protects you from a duplicate ticket if a 3-D Secure redirect causes a retry. Travel adds one twist: airline-specific fees or fare changes after an initial authorisation may need a fresh customer-authenticated payment rather than a silent re-charge.
GDPR roles in a typical European API integration
| Party | Typical GDPR role | What to put in writing |
|---|---|---|
| Your company (the retailer) | Controller of traveller data | Privacy notice, lawful basis, retention policy |
| Voraal, when it hosts and processes bookings | Processor acting on your instructions | Article 28 data processing agreement; standard contractual clauses, as Pakistan has no EU adequacy decision |
| Airlines, GDSs and hotel suppliers | Usually independent controllers for their own processing | Supplier terms; disclosure in your privacy notice |
| Payment provider | Depends on the provider and service | The provider's own terms and data agreement |
Roles depend on facts and contracts. Confirm with your data protection officer.
From sandbox to production
- 01
Scope the content
Agree which air, hotel, transfer, car and activity products you need and whether Avunzo runs on Voraal's supplier agreements or your own credentials.
- 02
Sign data terms
Data processing agreement and transfer clauses are signed before any real passenger data enters the system.
- 03
Build against the sandbox
Your developers receive sandbox keys, test data and the OpenAPI specification, and build search, price, book, fulfil and manage calls.
- 04
Wire in webhooks
Booking status and schedule-change webhooks feed your customer notifications and servicing queues instead of polling.
- 05
Certify and go live
An integration engineer reviews test bookings with your team, then production keys with per-key permissions and rate limits are issued.
Engineering checklist for European launches
- Store the 3-D Secure outcome and payment reference alongside the booking reference
- Send an idempotency key with every booking request
- Show NDC bundle contents and baggage rules before payment, not after
- Handle schedule-change webhooks within your customer-notification process
- Minimise passport and contact data to what each supplier actually requires
- Record the hosting region and sub-processors in your records of processing
Working with a Pakistan-based integration team
Voraal's engineers are in Pakistan, three to four hours ahead of Central European Time. Integration reviews and certification sessions take place in the shared working window, and asynchronous questions go through the ticketing desk. Documentation, release notes and the API reference are in English. For a structured pre-launch review, use the travel API integration checklist.
How Voraal delivers this
The product behind it.
FAQ
Frequently asked questions
Questions buyers ask about travel api integration for europe.
Ask us anythingDoes Avunzo itself perform 3-D Secure authentication?
No. Strong customer authentication is run by your payment service provider. Avunzo receives the booking once payment authorisation has succeeded, and idempotent booking requests prevent duplicate tickets if the payment step is retried.
Can we avoid GDS surcharges from European airlines through Avunzo?
Where an airline offers NDC content and the commercial agreement is in place, Avunzo can return that NDC offer alongside GDS fares, so your pricing logic can choose. Whether a surcharge applies depends on each carrier's current policy and your agreements, so check those directly.
Where is booking data stored when we use the API?
On Voraal-managed infrastructure unless agreed otherwise. Confirm the hosting region before contract and record it in your data processing agreement. If data must remain inside the EU under your own control, discuss a self-hosted arrangement as a scoped enterprise project.
How long does a European Avunzo integration take?
It depends on your scope and your team's capacity rather than on geography. Teams with an existing booking front end typically spend most of their time on payment flows, servicing and NDC display rules, not on search.
Can we keep our own NDC and GDS agreements?
Yes. Avunzo can run on your own credentials, which keeps your negotiated fares and airline relationships intact, or on Voraal's agreements where the supplier allows it.
Do the PSD3 and PSR changes require rework now?
Not immediately. They apply after formal adoption and a transition period. Because SCA sits with your payment provider, most of the change will arrive through provider updates. Keep authentication outcomes and payment references well structured so later adjustments are small.
Sources and further reading
- Business Travel News Europe: Lufthansa Group to increase DCC fee
- Stripe documentation: Strong Customer Authentication exemptions
- Arthur Cox: PSD3 and PSR final compromise texts published
- GDPR Article 28: Processor
- European Commission: adequacy decisions
Regulations, airline programmes and supplier terms change. Confirm requirements with the relevant authority or supplier before acting. Contact [email protected] if you spot something out of date.
Let’s build what comes next.
Tell us how your travel business works. We’ll recommend the right products and walk you through them on your own use case.