APIS Requirements – When, Where, and How

What Is APIS (Advance Passenger Information System)?

Advance Passenger Information System, commonly referred to as APIS, is a regulatory requirement used by government authorities to collect passenger and crew information in advance of an aircraft’s arrival or departure. APIS plays a role in border security processes by enabling authorities to review traveler data before a flight operates across international boundaries.

When planning an international flight, operators must consider a wide range of regulatory obligations. Compliance does not stop at the regulations of the home country. Entry and departure requirements for every destination and transit country must also be addressed. These requirements typically extend across customs, immigration, and quarantine procedures, often referred to collectively as CIQ processes. APIS is one of the mechanisms increasingly used by countries to support these processes and strengthen oversight of inbound and outbound flights.

It is important to distinguish APIS from the electronic APIS, or eAPIS, portal. APIS refers to the overall requirement and data set that must be submitted, while eAPIS is the U.S. Customs and Border Protection online platform through which APIS data is filed for U.S.-related flights. Other countries may use different systems or interfaces, but the underlying purpose of APIS remains consistent.

APIS requirements are becoming more common worldwide. Many countries now mandate APIS submissions both for arrivals and departures, and the number of jurisdictions enforcing these requirements continues to increase. In some regions, APIS notifications are also required for flights operating within the same group of countries, not only for international entries.

When Must APIS Be Submitted?

APIS submission timelines vary depending on the country and the nature of the flight. Operators must ensure that notifications are sent within the specific minimum and maximum lead times defined by the relevant authority.

For the United States, APIS submissions are subject to clearly defined timing rules. Passenger information must generally be submitted no later than 30 minutes prior to departure, while crew and non-crew information is typically required at least 60 minutes before departure. These timelines are enforced to ensure that data is reviewed before the aircraft becomes airborne.

Other countries may apply different rules. Some jurisdictions do not publish a fixed minimum lead time, while others enforce both minimum and maximum submission windows. Failure to submit within the required timeframe can result in the notification falling out of the system, which may lead to compliance issues and operational delays.

Special operating scenarios can further complicate APIS timing requirements. Flights such as medical evacuations, diversions, domestic continuations, or overflights may be subject to additional considerations depending on the country involved. Because these situations often require rapid operational decisions, understanding APIS obligations in advance is critical to avoid disruptions during execution.

Ultimately, operators are responsible for ensuring that APIS notifications are submitted in accordance with the requirements of every country to and from which they are traveling. Familiarity with country-specific timelines is essential to maintain compliance and support smooth flight operations.

Where to Submit the APIS Data

The method for submitting APIS data depends on the country and the type of operation. In the United States, APIS information is submitted through the eAPIS online system provided by Customs and Border Protection. This platform allows operators to enter passenger and crew data directly, provided they are registered and approved to use the system.

Outside of the United States, many countries operate their own portals or interfaces for APIS submissions. Operators must typically complete a registration process before making their first submission and can then access the system as required for subsequent flights.

In addition to government-run portals, many third-party service providers operate approved systems that can submit APIS notifications on behalf of operators. These systems are often integrated into broader trip support or flight planning workflows and are designed to meet the technical requirements of multiple jurisdictions.

For certain destinations, local ground handling agents may also be able to assist with APIS submissions, particularly for countries outside the U.S. While this can be a practical option, operators must still ensure that the information is submitted accurately and within the required timelines.

It is important to note that APIS submission methods may differ between private and charter operations. Some countries apply distinct formats or data handling rules depending on the classification of the flight. Understanding these differences is essential to avoid misclassification and potential compliance issues.

What Data Is Required in APIS?

While the specific interface and submission method may vary by country, the core data required for APIS is generally consistent across jurisdictions. The information must be entered exactly as it appears on official travel documents to ensure accuracy and acceptance by the receiving authority.

Standard passenger and crew data commonly required includes:

• Full name, exactly as listed on the traveler’s passport
• Date of birth
• Passport number, country of issue, and passport expiry date
• Nationality
• Gender

For non-U.S. residents traveling to the United States, a local address during their stay in the U.S. is also required.

For private aircraft operations, additional details are typically required as part of the APIS submission. These may include the aircraft tail number, itinerary information, pilot details, owner or operator contact information, and an emergency contact.

Commercial or charter operations often require a broader set of data. In addition to the core passenger information, submissions may include full crew member lists, detailed passenger identities, and supporting travel document information. Because requirements can differ between private and commercial flights, accurate classification of the operation is essential before submitting APIS data.

Common Pitfalls and Compliance Tips

One of the most common issues encountered with APIS compliance is the misclassification of the flight type. Treating a charter flight as a private operation, or vice versa, can result in incorrect data submission. This may lead to delays, system rejections, or potential fines imposed by the relevant authority.

Another frequent misunderstanding is assuming that APIS submission fulfills all border entry requirements. APIS notifications do not replace customs arrangements. Operators must still coordinate separately with the appropriate customs and border protection offices to obtain clearance. Filing APIS alone does not grant permission to land or clear customs.

Accuracy and timing are equally important. Submitting incorrect passenger details or missing the required lead time can cause the submission to fall out of the system. Once this happens, compliance may be jeopardized, and corrective action may be required before the flight can proceed.

Given the variation in requirements between countries, operators are encouraged to work closely with third-party service providers who manage APIS submissions regularly. These providers are positioned to maintain current knowledge of regulatory requirements and can help ensure that notifications are filed correctly and on time.

Summary and Key Takeaways

APIS is a critical component of international flight compliance and plays a role in supporting border security and CIQ processes. As more countries adopt APIS requirements, operators must be prepared to manage submissions accurately and within defined timelines.

The eAPIS portal serves as the primary submission platform for U.S.-related flights, while other countries rely on their own systems or approved vendor solutions. Regardless of the method used, accurate data entry and proper timing are essential to avoid operational disruptions.

Operators should always remember that submitting APIS does not replace customs notifications or landing permission requirements. Both processes must be coordinated separately to ensure smooth entry and departure.

Understanding when, where, and how to submit APIS data is essential for maintaining compliance and supporting efficient international operations.

To discuss your operational requirements or request trip support assistance, please contact UAS.