This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Advanced Passenger Information
The authorities of certain countries require airlines to transmit Advance Passenger Information (API) for all passengers flying to or via their country before departure. Passengers can provide their Advance Passenger Information data during check-in (Web Check-in or Kiosk Check-in in Airport) or using online form. Some airlines such as Air Canada, easyjet, emirates, american airlines, singapore airlines, air france, qatar airways, etihad, and iberia allow the passengers to provide API using online form to enter required information before they go to the airport. Passengers won’t be asked to provide the passenger information again when checking in. Any inaccurate or incomplete data provided could delay the journey, either at check-in or with the immigration authorities. Those passengers who refuse to supply API will be refused entry to these countries and therefore will not be allowed to travel.
Advanced Passenger Information vendors
| # | Name | Continent | Country | Documents |
|
Transmission Time | Transmission types | Details |
|---|---|---|---|---|---|---|---|---|
| 1 | USA APIS | North America |  |
No later than 1 hour before scheduled take off | Air Industry Networks/eAPIS Web service/Software VPN Internet Solution/Hardware VPN Internet Solution/Dedicated MPLS Communications | |||
| 2 | Canada API/PNR | North America |  |
Not later than the time of departure | MQ network/E-mail/Internet API Gateway/IDE | |||
| 3 | Mexico APIS | North America |  |
30 minutes prior to takeoff | UN/EDIFACT PAXLST (non-interactive) | |||
| 4 | Cuba APIS | North America |  |
- | SITA Network/ Email/ WebPortal | |||
| 5 | Australia APP | Australia |  |
- | - | |||
| 6 | UK iAPI | Europe |  |
Between STD -24hours and STD -30 minutes. | HTTPS/HTTP/(S)FTP/Web Services/IBM MQ/Network Protocol | |||
| 7 | Swiss API | Europe |  |
Immediately after departure | TYPE B message/ WebUpload application/ Fax | |||
| 8 | France API-PNR | Europe |  |
At the flight closure/Actual Time Departure | MQ connector, SOAP Web service, FTP, Historical networks, Manual entry in forms, Data entry by an HTML web form, Data entry by an Excel form | |||
| 9 | Germany APIS | Europe |  |
60 minutes prior to the actual arrival time | TYPE B message/e-mail | |||
| 10 | Netherlands API | Europe |  |
Within 15 minutes after “off blocks” | IATA Type B message format as UN/EDIFACT PAXLSTs/ Email | |||
| 11 | Finland API | Europe |  |
No later than 15 minutes after the flight‟s departure | IATA Type B message format as UN/EDIFACT PAXLSTs/ Email | |||
| 12 | Russia API | Europe |  |
15 min before Estimated Time of Departure | SITATEX Type B protocol/ FTP/Web Portal | |||
| 13 | Hungary API | Europe |  |
Immediately after takeoff | (S)FTP/IBM MQ/HTTPS | |||
| 14 | Estonia API | Europe |  |
Within 15 minutes after flight closure | Web service/ SOAP-XML/MQ/FTP/Web Portal | |||
| 15 | Peru APIS | South America |  |
Within 15 minutes after flight closure | - | |||
| 16 | Caribbean Community APIS | South America |  |
No later than 15 Minutes after Departure | SITATEX Type B protocol/ fax/email/webportal | |||
| 17 | China API | Asia |  |
- | SITA Type-B/ Web-based Application | |||
| 18 | India APIS | Asia |  |
Within 15 minutes of taking off of the aircraft | SITA Type B | |||
| 19 | Qatar APP | Asia |  |
Actual time of departure | Integrated APP/Carrier Portal | |||
| 20 | UAE API | Asia |  |
Actual time of departure | SITA Type B | |||
| 21 | Bahrain API | Asia |  |
Actual time of departure | SITA Type B | |||
| 22 | Lebanon API | Asia |  |
Actual time of departure | SITA Type B | |||
| 23 | Maldives API | Asia |  |
Within 15 minutes of flight departure (for inbound flight) and within 15 minutes after the passenger check-in has been closed (for out bound flight) | ||||
| 24 | South Africa API | Africa |  |
Actual time of departure | SITA Type B | |||
| 25 | Sri Lanka API | Asia |  |
Not later than 15 min of leaving or taking off of the airport | web portal | |||
| 26 | Indonesia API | Asia |  |
At Time of Departure | HTTPS,SMTP,IBM WebSphere MQ,Other Protocols | |||
| 27 | Thailand APPS | Asia |  |
Actual time of departure | SITA Type B |
Customers
Advance Passenger Information System
The purpose of advance passenger information
The immigration authorities of many countries require all airlines to provide passenger passport information prior to departure of any inbound or outbound flights to ensure safety and security.
Read MoreThe purpose of API is to give international governments and agencies the ability to screen passengers in advance of arrival in the destination country. API must be delivered a minimum of 20 minutes (U.S.) before flight departure. Information is screened, and returned with any ‘persons of interest’ flagged. - Advance Passenger Processing Advance Passenger Processing is a standard for flight and document data declaration in real-time. It has strong similarities with APIS in terms of what Traveller and flight data the government receives. The key difference is timing. APP takes place as a real-time interactive transaction during check-in. This enables the government to check databases of passports, visas, alerts, and according to government-dictated business rules, deny or allow boarding.
Advanced Passenger Information
Advanced Passenger Information (API) data are basic information that identify air travelers, collected during the check-in, and using the PAXLST message (WCO, ICAO and IATA standard).
Read MoreThe Advance Passenger Information System (APIS) is an electronic data interchange system established ORIGINALY by U.S. Customs and Border Protection, but also utilized by some other countries. APIS currently used by governments and those planned for future implementation can be placed in two distinct processes, each having unique features and delivering specific results.
Batch API
Non-interactive batch style API data covering all passengers and, in many cases, all crew members on board a specific flight are gathered during the check-in process and then transmitted in a single manifest message at or immediately following flight reconciliation or departure.
Interactive advance passenger information (iAPI)
An alternative to the batch style approach to API is an interactive API (iAPI) system allowing two way communication, in near real-time, on a passenger-by-passenger or transaction by transaction basis, which is initiated during check-in.
APIS Data
Required passenger information for all API countries (note that additional information requirements vary by country):
Read More- Official Travel Document Number - Issuing State or Organization of the Official Travel Document - Official Travel Document Type - Expiration Date of Official Travel Document - Surname/Given Name(s) - Nationality - Date of Birth - Gender - Seating Information - Baggage Information - Traveler‟s Status - Place/Port of Original Embarkation - Place of Birth - Visa Number - Issue Date of the Visa
Passenger Name Record (PNR)
Passenger Name Record (PNR) data are traveler flight reservation and itinerary information collected by air carriers (or their data providers).
Read MoreSpecific PNR data collected may change according to air carriers. It includes: type of ticket, date of travel, number of bags, seating information, etc. This type of information is in the commercial carriers’ reservation systems.
Which countries require advance passenger information?
The full list of all countries requiring Advance Passenger Information are as below: - Algeria - Antigua - Argentina - Australia - Bahamas
Read More- Barbados
- Bermuda
- Brazil
- Canada
- Cayman Islands
- China
- Colombia
- Costa Rica
- Cuba
- Denmark
- Dominican Republic
- France
- Germany
- Grenada
- Haiti
- Hungary
- Iceland
- Italy
- India
- Indonesia
- Jamaica
- Japan
- Kenya
- Mexico
- Netherlands
- New Zealand
- Pakistan
- Panama
- Portugal
- Qatar
- Romania
- Russia
- Saint Lucia
- Saudi Arabia
- South Africa
- South Korea
- Spain
- St Kitts and Nevis
- Taiwan
- Thailand
- United Arab Emirates
- United Kingdom
- United States
- Ukraine
- Vietnam
Access to PNR is required in 25 countries today and this number is continuously growing.
Benefits of Standard Transmission
- Faster implementation - Better compliance - Cost control - Reliable data - Minimum impact on airport infrastructure Source: https://www.iata.org/publications/api-pnr-toolkit/Pages/index.aspx
