FL3XX Developer Portal | FL3XX Developer Portal

Trip Support Providers play a crucial role in aviation operations by managing essential flight documentation and permissions. This guide explains how to use the FL3XX API to manage flight permits, airport slots, and PPRs (Prior Permission Required) for operators.

💡 Why Trip Support Providers Matter

🛡️

Regulatory Compliance: Ensure flights have all required permits and permissions before operations

⚡

Operational Efficiency: Streamline permit and slot management processes with automated workflows

📊

Real-time Tracking: Monitor permit and slot statuses to ensure timely approvals

🔗

Seamless Integration: Connect your trip support systems with FL3XX for unified flight management

🎯

Understanding Trip Providers

Learn the core concepts and responsibilities

Step 1

What is a Trip Support Provider?

A Trip Support Provider is a partner that manages flight-related documentation and services on behalf of operators. As a Trip Support Provider, you are a key part of the flight operation — handling permits, slots, PPRs, and ground services such as FBO, hotel, catering, and transport.

🎯 Core Responsibilities

Trip Support Providers are responsible for:

Creating and managing flight permits for takeoff, landing, and overflight permissions
Handling airport slot allocations and PPR (Prior Permission Required) requests
Uploading and managing permit and slot documentation
Updating permit and slot statuses as approvals are received
Ensuring compliance with regulatory requirements before flight operations
Managing ground services including FBO handling, hotel accommodation, catering, and transport arrangements

🔄 Assignment Workflow

The trip support provider workflow begins with flight assignment:

Step 1 - Operator Assignment: The operator must first assign you (the trip support provider) to a specific flight. This assignment is done by the operator through their FL3XX system.
Step 2 - Webhook Notification: Once assigned to a flight, you will receive a webhook notification (e.g. FLIGHT_PERMIT_ASSIGNMENT, FLIGHT_SLOT_PPR_ASSIGNMENT, FLIGHT_FBO_ASSIGNMENT). This is your signal to start managing items for that flight.
Step 3 - Permission Activation: After receiving the assignment notification, you have permissions to manage permits, slots, PPRs, and ground services for that flight. Without this assignment, you cannot add or edit any items.
Step 4 - Management Access: After assignment, you can use the API endpoints to create, update, retrieve, and delete permits, slots, PPRs, and ground services for the assigned flight.
Step 5 - Adding More Items: Once assigned to a flight, you can add multiple permits, slots, PPRs, and ground services as needed for that flight's operations.

Trip Support Provider Assignment Flow

👤

Operator Assigns

Provider to flight

→

🔓

Permissions Activated

API access enabled

→

➕

Manage Items

Create/update permits/slots/PPRs

→

📋

Add More Items

Multiple permits/slots/PPRs

🔑

Assignment Required

Important: You must be assigned to a flight before you can manage any permits, slots, PPRs, or ground services. Once assigned, you will receive a webhook notification (e.g. FLIGHT_PERMIT_ASSIGNMENT, FLIGHT_SLOT_PPR_ASSIGNMENT, FLIGHT_FBO_ASSIGNMENT) — this is your signal to start managing items for that flight. Once assigned, you have full access to manage all trip support items for that flight.

🔐 Scope and Access

All trip support operations are bound to the operator context and flight assignment:

You can only manage permits, slots, PPRs, and ground services for flights you have been assigned to
Assignment to a flight is required before you can create or edit any items
Once assigned, you can add multiple permits, slots, PPRs, and ground services for that flight
Each operator has their own isolated data context
Access is controlled through API authentication and flight assignment

📋 Flight Permits

Flight permits are official authorizations required for aircraft operations. They come in three types:

TAKEOFF: Permission required to take off from an airport
LANDING: Permission required to land at an airport
OVERFLIGHT: Permission required to overfly a country or airspace

Each permit has a status that tracks its approval state. Common statuses include REQ (Requested), OK (Confirmed), HOLD (On Hold), or DO (Done/Approved). Other available statuses include INIT, CNL (Cancelled), and revised versions (e.g., OK_REVISED).

✈️ Slots and PPRs

Airport slots and PPRs are time-specific permissions for airport operations:

SLOT: A specific time allocation at a coordinated airport
PPR: Prior Permission Required - advance approval needed before operating at certain airports

Both slots and PPRs can be associated with either DEPARTURE or ARRIVAL airports, and they track approval statuses similar to flight permits.

🔑

Operator Context

All trip support operations are scoped to the operator associated with your authentication token. As a partner, you can only manage permits, slots, PPRs, and ground services for flights within that operator's context. This ensures data isolation and security.

📋

Managing Flight Permits

Create, update, and manage flight permits

Step 2

✈️

Managing Slots & PPRs

Handle airport slots and PPR requests

Step 3

📄

Document Management

Upload and manage permit documents

Step 4

🔔

Event Notifications

Receive real-time updates via webhooks

Step 5

🛬

Managing FBO Services

Update and retrieve FBO handling services

Step 6

🚗

Managing Transport Services

Create, update, and manage transport arrangements

Step 7

🏨

Managing Hotel Services

Create, update, and manage hotel accommodations

Step 8

🍽️

Managing Catering Services

Create, update, and manage catering orders

Step 9

🛂

Migration

Manage passenger travel authorisation and submission statuses

Step 10

✅

Best Practices

Monitor Status Changes: Regularly check permit and slot/PPR statuses to ensure timely approvals. Use webhooks to receive real-time updates when provider assignments change.

Document Management: Upload permit and slot documents promptly after receiving approvals to maintain compliance records. Ensure documents are in supported formats and within size limits.

Error Handling: Implement robust error handling for API calls, especially when creating or updating permits. Handle rate limits and network errors gracefully.

Data Synchronization: Use webhooks to keep your systems synchronized with FL3XX, reducing the need for frequent polling and improving efficiency.

📖