Advance Passenger Information

Advance Passenger Information (API)

This is the information or data concerning a crew member, passenger or any other person travelling in an aircraft or vessel prior to arrival and departure.

The Twenty Seventh Meeting of the Conference of Heads of Government which was held in St. Kitts and Nevis in July 2006 agreed to the creation and establishment of the Joint Regional Communication Centre (JRCC).

The JRCC is a Sub-Agency of CARICOM IMPACS, an institution of CARICOM dedicated to enhancing the individual and collective law enforcement and border security capacity of CARICOM Member States.

The JRCC is mainly responsible for the operations and management of the Advance Passenger Information System (APIS), which screens Millions of passengers annually, specifically those entering, and travelling within the CARICOM Region by air and sea ports.

Advance Passenger Information System (APIS)

This means the automated electronic data interchange of API; and the screening of API by the competent authority (St. Kitts and Nevis Immigration Department), IMPACS and the Joint Regional Communications Centre (JRCC) against a Watch List for any API.

Duty to provide advance passenger information

The captain or master of every aircraft or vessel expecting to arrive in or leave Saint Christopher and Nevis shall provide to the competent authority and IMPACS, the relevant API and data relating to the flight or voyage.

Guidelines for Submitting the API

In an effort to ensure the successful transmission and submission of API, the Joint Regional Communications Centre (JRCC) provides an environment which facilitates the transmission of API from all carriers and individuals. Hence it is advised to utilize this method of transmission via the JRCC Web Portal which can be accessed at for the submission of APIs. Please take a look at the Web Portal Guidelines. Additionally, it is recommended that you visit the Centre’s website for additional information and updates.


In case of commercial aircraft, no later than 40 minutes prior to departure from the last port of call;

In case of a private aircraft, no later than 40 minutes prior to the departure from the last port of call;

In case of a vessel arriving from outside the regional space, no later than 24 hours prior to arrival;

In case of a vessel arriving from a destination within the regional space, no later than I hour prior to the arrival of the vessel from the last port of call.

In the event of any changes to the flight/vessel header data or data relating to an individual on board, an updated API file is required prior to departure of the aircraft or vessel.

In the case of vessels and aircraft a API file is required five (5) minutes immediately following take-off.

Failure to submit API

A captain or master who fails to provide API or intentionally or recklessly provides erroneous, faulty, misleading, incomplete or false API or transmits the API in an incorrect format, commits an offence and is liable on summary conviction to a fine of ten thousand dollars or to imprisonment for a term of one year or to both such fine and imprisonment.

For further information please refer to the legislation section