Advance passenger information is not an API in the technology sense. Carriers must supply it by law. Under paragraph 27B of Schedule 2 to the Immigration Act 1971, the owner or agent of a ship or aircraft, called the carrier, must provide passenger information when an immigration officer asks for it in writing. GOV.UK calls this supplying travel document information, also known as API, to UK Border Force.

What is sent

Since 19 December 2024, the data has been set by the Immigration and Police (Passenger, Crew and Service Information) Order 2024, which replaced a 2008 order. The core items, as shown on the travel document, are:

• full name, sex, date of birth and nationality

• the document type, number, expiry date and issuing state

The order also lists booking data that carriers must give if they hold it, such as the itinerary, payment details and any travel agent used. This is passenger name record (PNR) data. A Home Office direction, the latest applying since 7 January 2026, requires the document data to be sent electronically through a system that can receive replies.

Why it matters for travel businesses

• It can stop travel. Under the Authority to Carry Scheme 2023, sending the data counts as the carrier’s request for authority to carry each person. The Home Office can refuse authority, for example for someone refused an ETA or using a lost, stolen or expired passport. A carrier that breaches the scheme can face a financial penalty.

• Airlines ask for it in advance. The duty is the carrier’s, but airlines usually ask for API at booking or check-in. easyJet, for example, asks group bookers, including agents, for names and API no later than 5 days before departure.

• Mismatches cause delays. GOV.UK warns eVisa holders that a carrier cannot check their status automatically if their details and documents do not match the passenger information given.