🎯 Trip Support Providers
Complete guide to managing flight permits, slots, and PPRs as a Trip Support Provider using the FL3XX API
Understanding Trip Providers
Managing Flight Permits
Managing Slots & PPRs
Document Management
Event Notifications
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
Understanding Trip Providers
Learn the core concepts and responsibilities
What is a Trip Support Provider?
A Trip Support Provider is an external service provider that manages flight-related documentation and permissions on behalf of operators. They handle critical aspects of flight operations including permits, slots, and PPRs.
🎯 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
🔄 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 the operator assigns you to a flight, you will receive a webhook notification (
FLIGHT_PERMIT_ASSIGNMENTorFLIGHT_SLOT_PPR_ASSIGNMENT). This notification is how you know you have been assigned and need to start managing items for that flight. - Step 3 - Permission Activation: After receiving the assignment notification, you have permissions to manage permits, slots, and PPRs 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, and PPRs for the assigned flight.
- Step 5 - Adding More Items: Once assigned to a flight, you can add multiple permits, slots, and PPRs as needed for that flight's operations.
Trip Support Provider Assignment Flow
Assignment Required
Important: You must be assigned to a flight by the operator before you can manage any permits, slots, or PPRs. If you attempt to use the API endpoints without being assigned to a flight, your requests will fail. Once assigned, you will receive a webhook notification (FLIGHT_PERMIT_ASSIGNMENT or FLIGHT_SLOT_PPR_ASSIGNMENT) informing you of the 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, and PPRs for flights you have been assigned to by the operator
- Assignment to a flight is required before you can create or edit any items
- Once assigned, you can add multiple permits, slots, and PPRs 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. You can only manage permits, slots, and PPRs for flights that belong to your operator. This ensures data isolation and security.
Managing Flight Permits
Create, update, and manage flight permits
Managing Slots & PPRs
Handle airport slots and PPR requests
Document Management
Upload and manage permit documents
Event Notifications
Receive real-time updates via webhooks
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.
Flight Permits API Reference
View the complete API reference for flight permit endpoints
View Reference →Slots & PPRs API Reference
View the complete API reference for slot and PPR endpoints
View Reference →