Passenger data
EU Advance Passenger Information Regulations (EU) 2025/12 and 2025/13
Short answer
- Border regulation
- Regulation (EU) 2025/12 of 19 December 2024 1
- Law enforcement regulation
- Regulation (EU) 2025/13 of 19 December 2024 2
- Published
- Official Journal L series, 8 January 2025 1
- Router
- Designed, developed, hosted and managed by eu-LISA 4
- Retention by carriers
- 48 hours from receipt by the router 1
- Maximum penalty
- Up to 2% of global turnover for recurrent failure to transfer data 1
- Replaces
- Council Directive 2004/82/EC, from the date of application 1
Two regulations, two purposes
The European Commission proposed the two regulations in December 2022. A political agreement between the European Parliament and the Council followed on 1 March 2024, and the rules were formally adopted in December 2024 3. The Parliament adopted its first-reading position on 25 April 2024 by 492 votes to 33, with 10 abstentions 4.
Regulation (EU) 2025/12 deals with external border checks. The Commission says carriers must send API data for all passengers on flights into the Union to the competent border authorities 3. Regulation (EU) 2025/13 deals with law enforcement. The Commission says it covers all passengers and crew on extra-EU flights, and selected intra-EU flights where PNR data is collected, with data going to passenger information units 3.
What carriers must collect and send
Article 2 of Regulation (EU) 2025/12 says it applies to air carriers conducting flights into the Union 1. Recital 7 excludes flight schools, medical, emergency and military flights. It asks the Commission to assess whether a scheme for private flights is feasible 1.
Article 4(2) lists the passenger data. It includes surname and given names, date of birth, sex, nationality, travel document details, the PNR record locator, seat and baggage information where available 1. Article 5 requires carriers to collect identity data by automated means from the machine-readable data of the travel document. Manual collection is allowed only where automated means are not technically possible 1.
Under Article 6(2), carriers transfer data for each passenger at check-in, no earlier than 48 hours before scheduled departure. They send it again for boarded passengers immediately after flight closure 1.
The central router
The European Parliament summary says eu-LISA, the EU agency for large-scale IT systems, should design, develop, host and technically manage a router for encrypted API data 4. The router checks in real time whether carriers have sent the data and alerts the carrier and authorities if not 4.
Article 34 says the Commission will set the date the router starts operations by implementing act, once eu-LISA reports that a full test of the router was successful 1. The Commission says the law enforcement regulation requires carriers to send PNR data through the same router in a phased approach 3. The Swiss State Secretariat for Migration (SEM) says the router will replace the many separate connections between carriers and national authorities 5.
Retention, audits and penalties
- Carriers keep API data for 48 hours from receipt by the router. Border authorities keep it for 48 hours, with an extra 48 hours in exceptional cases for passengers who have not yet presented at a border crossing point 1.
- National data protection authorities audit border authorities at least once every four years. The European Data Protection Supervisor audits eu-LISA at least once a year 1.
- Article 37(4) sets penalties of up to 2% of the carrier's global turnover of the preceding financial year for recurrent failure to transfer API data 1.
Timeline and status
| Date | Event | Status |
|---|---|---|
| December 2022 3 | Commission proposes two API regulations 3 | Historical 3 |
| 1 March 2024 3 | Political agreement between Parliament and Council 3 | Historical 3 |
| 25 April 2024 4 | Parliament first-reading vote, 492 to 33 with 10 abstentions 4 | Historical 4 |
| 12 December 2024 5 | Adopted and notified to Switzerland, according to SEM 5 | Historical 5 |
| 19 December 2024 2 | Date of both regulations 1,2 | Historical 1,2 |
| 28 January 2025 2 | Both regulations enter into force 1,2 | In force 1,2 |
| 29 January 2026 1 | Deadline for the first yearly eu-LISA report on router development 1 | Legal deadline, report not checked 1 |
| 29 January 2029 1 | Deadline for the first Commission overall evaluation 1 | Legal deadline 1 |
| About 2031 5 | Full application two years after the router starts, SEM estimate 5 | Proposed timeline 5 |
Switzerland and the Schengen area
SEM says Regulation (EU) 2025/12 is a development of the Schengen acquis under Switzerland's association agreement and that SEM is responsible for implementing it 5. Its page, last modified 31 August 2026, says the rules will not be fully applied until two years after the router enters operation, probably 2031 5. SEM says the border management rules apply to flights arriving in an EU country from a third country 5. The text of Article 46 of Regulation (EU) 2025/12, which sets its date of application, could not be opened for this page, so the 2031 date is SEM's estimate only 1,5.
Common questions
When do the new EU API rules apply?
They entered into force on 28 January 2025 1. SEM says full application comes two years after the router starts, probably 2031 5.
What is the EU API router?
A central system built and managed by eu-LISA to pass encrypted API data from carriers to authorities 4.
Do the EU API rules cover private flights?
The border regulation does not cover them in its operative text. Recital 7 asks the Commission to assess a scheme for private flights 1.
How long can airlines keep API data?
48 hours from receipt by the router, under Article 8(1) of Regulation (EU) 2025/12 1.
What fine can an airline face?
Up to 2% of global turnover of the preceding financial year for recurrent failure to transfer API data 1.
Rules and charges change. Check the official source linked on this page before you pay or travel. Spotted an error? Email hello@digitalborderdirectory.com.
Sources
- EUR-Lex: Regulation (EU) 2025/12 of the European Parliament and of the Council on the collection and transfer of advance passenger information for external border checks, repealing Council Directive 2004/82/EC (19 December 2024)
- EUR-Lex: Regulation (EU) 2025/13 of the European Parliament and of the Council of 19 December 2024 on the collection and transfer of advance passenger information for the prevention, detection, investigation and prosecution of terrorist offences and serious crime (19 December 2024)
- European Commission, Migration and Home Affairs: Travel Information, Passenger Name Record (4 August 2026)
- European Parliament Legislative Observatory: Collection and transfer of advance passenger information for enhancing and facilitating external border controls, document summary (25 April 2024)
- State Secretariat for Migration SEM, Switzerland: Advance Passenger Information (API) (last modified 31 August 2026)
Related
- Advance passenger information (API) and interactive API
What advance passenger information and interactive API are, what airlines send, the ICAO Annex 9 standards, UN resolutions and the EU API rules.
- Passenger name record (PNR) data
What PNR data is, how it differs from API, the ICAO PNR standards of 2020, the EU PNR Directive and the EU's PNR agreements with other countries.
- EU PNR Directive (EU) 2016/681
The EU PNR Directive 2016/681: scope, passenger information units, five-year retention, the 2022 EU Court of Justice ruling and the Commission's reviews.
- US CBP Advance Passenger Information System (APIS) and TSA Secure Flight
Airlines flying to the US send passenger manifests to CBP's APIS under 19 CFR 122.49a. TSA's Secure Flight matches passenger data against watch lists.
- EU Entry/Exit System (EES)
The EES registers non-EU short-stay travellers with fingerprints and a facial image at Schengen borders. Fully operational since 10 April 2026.