API/PNR System
A streamlined, secure, and scalable solution for enhancing aviation security, operational efficiency, and passenger experience in compliance with global standards set by ICAO, WCO and IATA.
Advance Passenger Information (API)
API (Advance Passenger Information) refers to a set of data provided by airlines to border control agencies about passengers before their arrival or departure. This data typically includes biographical details such as name, date of birth, nationality, and travel document information. The purpose of API is to enhance border security, facilitate risk assessment, and streamline immigration processes by allowing authorities to process passenger information in advance of their travel.
Passenger Name Record (PNR)
PNR (Passenger Name Record) is a record in the database of an airline or travel agency containing the travel itinerary and associated details of a passenger or group of passengers. It includes information such as the passenger’s name, contact details, ticketing information, travel dates, seat preferences, and other special requests. While primarily created for the airline’s business purposes, PNR data is also shared with states to assist in security, immigration, and law enforcement processes.
Benefits
The standard transmission of API/PNR data offers several key benefits for the aviation industry:
Faster Implementation: Standardized data formats and protocols streamline the integration process, allowing airports and airlines to quickly adopt the system and meet regulatory requirements without custom modifications.
Better Compliance: By adhering to internationally recognized standards, such as those set by ICAO, IATA, and the WCO, API/PNR systems ensure consistent compliance with global aviation security and data-sharing regulations, minimizing the risk of non-compliance.
Cost Control: Standard transmission reduces the need for costly custom systems or ongoing adjustments. It also minimizes the costs of training and maintenance by using a unified approach across different stakeholders, from airlines to border control agencies.
Reliable Data: The use of internationally defined message formats ensures high-quality, accurate, and consistent data transmission, reducing errors and improving the reliability of passenger information exchange.
Minimum Impact on Airport Infrastructure: Since the API/PNR system utilizes standardized formats, it requires less complex infrastructure updates at airports. This ensures a smooth integration with existing systems, reducing operational disruptions and minimizing additional investments in hardware and software.
ROCK AFRICA & ASCENT SOLUTIONS APPOINTED BY GCAA FOR the development and deployment of API/PNR System
Rock Africa and Ascent Solutions have partnered with Ghana’s Ministry of Transport and Civil Aviation Authority to develop and deploy an Advanced Passenger Information and Passenger Name Record System. The system will enhance passenger processing, security, and compliance with international aviation standards.
Read More on the Press Release
Learn More on the GCAA Directive
Stakeholder Engagement with Airlines on implementation of API and PNR
SYSTEM BASICS
Passenger data comprises of Advance Passenger Information (API) and Passenger Name Records (PNR). This data can be a useful tool for governments’ border control or security processing as it can help them pre-identify travelers and patterns.
Strong global standards and guidelines are in place to assist States. It is essential that States understand and follow them to ensure swift compliance by the airlines and maintain smooth passenger movements at airports.
IATA, International Civil Aviation Organization (ICAO) and World Customs Organization (WCO) have developed a toolkit which include introductory presentations and videos, dynamic checklists and reference material to help you design passenger data programs that are harmonized, efficient and valuable.
Privacy and Data Protection are critical when handling Passenger Name Record (PNR) data, as it contains personal information about travelers. Different countries have varying perspectives on what constitutes private data and how much of it can be shared, which can lead to complexities in international data exchange. In many cases, state-to-state agreements or memorandums of understanding may be necessary to ensure that data sharing is done in a compliant and secure manner. It’s important to note that not all sensitive data should be required for the API/PNR process—only the essential information needed to meet security and operational objectives should be collected and transmitted, ensuring the protection of passengers’ privacy.
The WCO, IATA, and ICAO have developed guidelines for both API and PNR, with the PNRGOV Working Group developing standards for reporting PNR information to governments.
- Protect airlines against data protection issues
- No more emailing manifest to government agencies
- No more printing of manifest
- Time saved on operational tasks
- Quicker turn around for flights
API format UN/EDIFACT PAXLST
PNR format UN/EDIFACT PNRGOV
- Scheduled Carriers (e.g. Commercial, Chartered and General Aviation Carriers) – passengers and crew;
- Cargo Carriers – crew;
- Unscheduled Carriers – passengers and crew
- MQ over VPN messaging
- Web Portal
- Legacy Type-B