Setting Up APIS in FOS
Setting up APIS in FOS
With FOS version 3.14.1 or better, the CBP credentials for eAPIS submission from FOS are managed at the provider level, via a shared API provided by U.S. Customs and Border Protection. The individual customer must still ensure their APIS credentials (91 and/or 135 are kept valid and password change requirements met with CBP directly).
To set up APIS in FOS you will need to confirm that the address and phone number fields on the General Tab of the Company Data as they will affect the information sent to APIS.
On the Interface Tab Marked APIS is where the user will input information specific to their company’s APIS account.
1. The top section will contain information relevant to only 135 and 121 operations.
2. You will need to determine how the flight number will be sent to APIS and there are several ways in which it may be done. The default will be, "Trip Number", to which FOS will append the leg number when the APIS report is sent. Or you can use the AC Tail Number, Leg Flt number, or AC flt Trk Num.
3. The two boxes "Send as E-Mail Attachment", and "Use SMTP E-Mail" are discouraged from being used since the Department of Homeland Security (DHS) prefers the APIS report transmitted via the web interface.
The middle section applies to both the UN/EDIFACT submission and submission for 91 operators. The “Allow Non-Fatal Errors” box will allow the system to submit the APIS report if there is any information missing from the report that DHS has determined is wanted but not mandatory, e.g. middle names. If you are a carrier registered outside of the United States, you must check the “Foreign Carrier” box.
The bottom section provides fields relevant to Part 91 operations only. The flight number field here will default to “Leg Flt Num”.
After the company Data has been completed you will need to confirm that the aircraft Owner Information is populated correctly.
Owner information may be entered in these fields. If you will be submitting information from APIS directly from FOS, you must create a record in the client/passenger database and link that company’s record using the lookup function. The “Owner Name” record in the client/passenger database may be accessed from that point on, when necessary, by using the “Owner Name” button.
Use Aircraft Company for APIS – When selected, this option uses the contact information from the company set in the “Company” code box rather than the information set in the “Owner Name” fields when filing private APIS.
Related Articles
Error: submitFlightManifest failed: APIS_91_WSDL: FOS2007.dll - Filing APIS
Error: The attempt to send APIS data has failed. apisSoal->submitFlightManifest failed : APIS_91_WSDL::Send_APIS_SOAP() : APIS_91_Unit.cpp : FOS2007.dll SOAP message: An error occurred in the secure channel support System Exception: An error occurred ...eAPIS Tech Support: How to update password
FOS will continue to integrate with the eAPIS web service. Instead of using customer credentials, FOS will utilize credentials managed in Flight Manager (FM). FOS Tech support updates the eAPIS credentials inside FM internal every 45 days. FM will ...Interfaces Tab - APIS
The APIS section permits the user to input information specific to their company’s APIS account. See below pertaining to Password fields for those on FOS version 3.14.1 or better. (Main View of Interfaces Tab - APIS) “UN/EDIFACT” Section - Contains ...Error: Access is denied (when submitting APIS)
Error: Access is denied. Solution: Ensure user has at least "Modify" permissions to the FOS Data / Picture folder on the FOS server. If the customer is hosted, FOS Support will arrange for the permission to be re-applied by the Application Support ...Error Message for APIS 91 - APIS error 403
If your client receives the following error message, please reach out to Eric Rodriguez (ERIC.M.RODRIGUEZ@CBP.DHS.GOV) to verify that the Sender ID's have the web service for certification or if the web service has been stopped. Attempt to send APIS ...