Setting Up APIS in FOS

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 enter their APIS Sender ID. The password is not longer required in FOS, but the customer needs to ensure they are keeping their account valid by changing the password on the CBP site at the required interval. 

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. 
4. 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 is set properly.

For 135 submissions: Owner Information should be populated correctly. Owner information may be entered in these fields. If you will be submitting information from APIS directly from FOS, for 135, 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. 


For 91 submissions: You will have three options (as of FOS version 3.16), to choose where in FOS the "Operating Company" will pull from.
  1. Use User's Company for APIS 91 - The company set in the user profile of the person submitting the APIS will be reflected.
  2. Use Aircraft Company for APIS 91 - The company set in the aircraft profile, Company field drop down will be reflected.
  3. Use Owner Name for APIS 91 - The Owner Name set in the aircraft profile will be reflected.

(Images showing where the options point to).


   





(Image showing how/where the option is reflected on the APIS submission).



    • Related Articles

    • FOS Release Notes (3.15.1)

      FOS® Release Notes – Version 3.15.1 Release Date: August 2025 Enhancements 1. FOS Mobile Enhancement: FOS can now send passenger profile pictures to FOS Mobile. Please note that only the image set in the Picture Tab of the passenger record will be ...

    • 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 ...

    • 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) "APIS" Section This section ...

    • Error: new failed TrioDM : APIS_91_WSDL::InitAPIS : APIS_91_UNIT : FosMobile.dll System Message: Microsoft MSXML is not installed

      The following error may be seen on a user-by-user basis when attempting to file 91 APIS from FOS. Error: new failed TrioDM ; APIS_91_WSDL::InitAPIS : APIS_91_UNIT : FosMobile.dll System Message: Microsoft MSXML is not installed Solution: This is a ...

    • 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 ...