Differences between API I and API II
[Reference ICAO Annex 9, Chapter 9, Section B] – Advance Passenger Information (API) systems play a critical role in modern aviation security, allowing for the pre-arrival vetting of passengers by collecting and transmitting their data to destination country authorities. These systems help improve border security, streamline immigration processes, and enhance overall travel facilitation. API systems are divided into two types: Standard API (API I) and Interactive API (API II), each with its own methods of data transmission and interaction with authorities.
API I (Standard API)
- Overview: Standard API (API I) is a one-way transmission of passenger data from airlines to the government authorities of the destination country. This system is used for vetting passengers before the flight departs and allows the authorities to screen passengers based on predefined security or immigration criteria.
- Data Transmission: Airlines send a complete list of passengers to the border authorities after check-in but before the flight departs. This typically includes basic biographical details such as name, date of birth, nationality, passport number, and flight details.
- Response from Authorities: API I systems do not involve real-time communication. Once the authorities receive the data, they conduct background checks and determine any actions, such as flagging passengers for further inspection on arrival.
- Processing Time: Since API I is not interactive, any decisions on passenger admissibility are usually made after the passenger is already in transit. This means that passengers who are inadmissible may only be intercepted after landing, which could lead to delays at immigration.
API II (Interactive API or iAPI)
- Overview: Interactive API (API II or iAPI) provides a more dynamic system where data is transmitted during the check-in process. Authorities are involved in real-time, which means they can provide feedback to airlines before the passenger boards the flight.
- Data Transmission: As passengers check in, their data is immediately sent to the destination country’s authorities. This system is two-way, meaning authorities can quickly return decisions regarding each passenger’s admissibility. If a passenger is flagged, the airline will be notified in real-time, allowing the airline to refuse boarding.
- Response from Authorities: The key difference with API II is that it allows immediate feedback. Authorities have the opportunity to vet and approve or deny entry before the passenger boards the aircraft, thereby reducing the risk of inadmissible passengers arriving at the destination airport.
- Processing Time: The entire process is more efficient, as decisions are made before departure, reducing the need for post-arrival inspections and lowering the possibility of immigration issues after landing. It also helps avoid unnecessary deportations and penalties for airlines.
Key Differences
- Data Flow: API I is a one-way transmission, while API II allows for two-way communication between airlines and border authorities.
- Timing: In API I, data is sent after check-in but before departure, with no real-time interaction. In API II, data is sent at check-in, and responses are received almost immediately.
- Passenger Admissibility: API I informs authorities about passengers, but decisions on admissibility are usually made after the flight departs. In contrast, API II allows authorities to make real-time decisions, preventing inadmissible passengers from boarding in the first place.
- Efficiency: API II is more efficient for both airlines and authorities, as it helps avoid potential issues at the destination and enhances security by preventing unauthorized travel at the point of departure.
Conclusion
While both API I and API II aim to enhance security and facilitate passenger data sharing, API II is a more advanced and efficient system that benefits from real-time communication and decision-making. It helps authorities act proactively, improving border control processes and reducing risks for airlines