Initial Setup in Avianis

Create Webhook

1. Navigate to the eu-LISA integration configuration page

2. Click Create Webhook

3. Avianis automatically creates and registers the webhook with eu-LISA
   

1. Once the webhook is successfully created, the button updates to green and displays "Webhook Created"

4. Enter the verification code provided by eu-LISA into the Verification Code field

5. Save to confirm and activate the integration.

1. Navigate to Operations > Operations Settings > APIS Settings
2. Select eu-LISA
3. Click Save

No additional configuration is required. This enables eu-LISA handling for applicable flight legs.

Automated Submissions

eu-LISA requires at least one submission within 48 hours of departure. Avianis handles this automatically through a background process.

How Automated Submissions Work

• A background process continuously monitors flights departing within 48 hours
  
• Passenger and crew data is automatically submitted or re-submitted as needed
• Multiple submissions are allowed and may occur automatically
• Pets are automatically excluded from submissions
• All submission responses are logged in the Activity Feed
  

What Triggers Automatic Submissions

Avianis will automatically submit to eu-LISA when:

• A passenger or crew member is added or removed from the flight
• Travel documents are saved or changed
• Trip or leg details are updated
• The flight enters the 48-hour departure window

Manual Submissions

While Avianis handles most submissions automatically, you can manually submit or re-submit passenger data at any time.

Expand the APIS section of the feasibility in the trip in which you are submitting the manifest.

Click "Submit [Country]" next to the appropriate location.

1. All passengers and crew will be listed in the popup modal
2. For each traveler:
   • Confirm or select the appropriate passport from the dropdown
   • Confirm the address
3. Click "Validate". Validation errors display inline under each passenger or crew member in the submission modal. Resolve all errors before submitting.
4. Click "Submit". Once all passengers and crew have been successfully validated a Submit button appears. 

Validation Requirements

Before any submission, Avianis validates passenger data to ensure compliance with eu-LISA requirements.

Required Fields:

• Travel Document Country: Must be a valid ISO country code that aligns with the flight's routing
• Travel Document Expiration Date: Must not be before the leg's departure date
• Date of Birth: Required
• Sex: Required (male, female, or unspecified)
• Nationality: Required
  

Understanding Submission Results

After each submission, eu-LISA returns a status for every passenger and crew member.

Status Codes:

• OK – Passenger verification successful

• NOK EES – Verification failed due to EES rules

• NOK ETIAS – Verification failed due to ETIAS rules

• NA – Traveler is out of scope

A single traveler may receive multiple status codes (e.g., both NOK EES and NOK ETIAS).

Where to View Results

eu-LISA submission results are displayed in multiple locations throughout Avianis for easy visibility.

1. Submission Modal

• Results appear immediately after manual submission
• Shows status for each passenger and crew member
  

2. APIS Section (Feasibility & Tools)

• Status appears in the expanded APIS section
• Displays count of passengers by status (e.g., "3 OK, 1 NOK")
• Section displays in red if any traveler has a status other than OK or NA, or if changes have been made that require resubmission
  

3. Passenger and Crew Tabs

• Status icon displays next to each passenger and crew name
• Alerts appear on the tab when a status other than OK is returned
  

4. Activity Feed

• Complete log of all eu-LISA submissions and responses
• Shows both automatic and manual submissions
  

Email Notifications

Avianis automatically sends email notifications for submission failures to ensure you're aware of compliance issues.

When Notifications Are Sent:

• Sent: Only for flights departing within 48 hours
• Not Sent: For flights departing more than 48 hours out
• Timing: Based on scheduled departure time (not submission time)

This ensures you receive alerts only when action is urgently needed for compliance, while avoiding notification fatigue for early submissions.