# FL3XX API

<div class="api-wrapper">

  <!-- Beta Banner -->
  <div class="api-beta-banner">
    <div class="api-beta-content">
      <div class="api-beta-icon">
        <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
          <path d="M12 2L2 7l10 5 10-5-10-5z"></path>
          <path d="M2 17l10 5 10-5"></path>
          <path d="M2 12l10 5 10-5"></path>
        </svg>
      </div>
      <div class="api-beta-text">
        <h3 class="api-beta-title">FL3XX API v2.0 - Beta Release</h3>
        <p class="api-beta-subtitle">Currently in active development with our trusted beta partners. Experience the next generation of aviation API technology.</p>
      </div>
      <div class="api-beta-badge">BETA</div>
    </div>
  </div>
</div>

<style>
  /* Beta Banner */
  .api-beta-banner {
    background: linear-gradient(135deg, rgba(241, 90, 42, 0.05), rgba(241, 90, 42, 0.02));
    border: 2px solid rgba(241, 90, 42, 0.2);
    border-radius: 12px;
    padding: 20px;
    margin-bottom: 40px;
  }

  .api-beta-content {
    display: flex;
    align-items: center;
    gap: 16px;
  }

  .api-beta-icon {
    width: 48px;
    height: 48px;
    background: rgba(241, 90, 42, 0.1);
    border-radius: 12px;
    display: flex;
    align-items: center;
    justify-content: center;
    color: #f15a2a;
    flex-shrink: 0;
  }

  .api-beta-text {
    flex: 1;
  }

  .api-beta-title {
    font-size: 18px;
    font-weight: 700;
    color: var(--text-color-primary);
    margin: 0 0 6px 0;
  }

  .api-beta-subtitle {
    font-size: 14px;
    color: #6B7280;
    margin: 0;
    line-height: 1.4;
  }

  .api-beta-badge {
    background: #f15a2a;
    color: white;
    font-size: 12px;
    font-weight: 700;
    padding: 6px 12px;
    border-radius: 16px;
    text-transform: uppercase;
    letter-spacing: 0.5px;
    flex-shrink: 0;
  }
</style>


Version: 2.0.0
License: MIT

## Servers

Test Server
```
https://test.fl3xx.com
```

## Security

### X-Api-Client-Id

Type: apiKey
In: header
Name: X-Api-Client-Id

### X-Auth-Token

Type: apiKey
In: header
Name: X-Auth-Token

## Download OpenAPI description

[FL3XX API](https://developer.fl3xx.com/_spec/reference/@v2/index.yaml)

## Airports

Access comprehensive airport information.

**Business Value**
- Filter airports by various criteria including ICAO, IATA, FAA codes and local identifiers
- Support high-performance applications with optimized data retrieval

<br/>

**Use Cases**
- Filter airports by specific codes for targeted data retrieval
- Integrate airport data into flight planning and scheduling systems
- Build airport selection interfaces with efficient pagination

<br/>


### Get airport

 - [GET /api/v2/airports/{airportCode}](https://developer.fl3xx.com/reference/v2/airports/paths/~1api~1v2~1airports~1%7Bairportcode%7D/get.md): This endpoint provides efficient access to airport data.


- Multiple filter options (ICAO, IATA, FAA, local identifier)
- Automatic exclusion of deleted/inactive airports


## Airport Fuel Prices

Manage and optimize airport fuel pricing data for your organization. These endpoints enable operators to efficiently update, remove, and bulk-manage fuel prices, supporting streamlined fuel order workflows and provider management.

**Business Value**
- Ensure accurate and up-to-date fuel pricing for all airport operations.
- Reduce manual effort and errors by enabling bulk updates and deletions.
- Support cost control and negotiation with providers through transparent pricing data.
- Enhance operational planning and financial forecasting with reliable fuel cost data.

<br/>

**Use Cases**
- Update fuel prices for a specific airport to reflect new agreements or market changes.
- Remove outdated or incorrect fuel prices for compliance and data integrity.
- Perform bulk deletions to quickly adapt to network-wide pricing changes.
- Integrate with internal systems to automate fuel price management and reporting.

  <br/>

**Note:**  
> The data managed by the Airport Fuel Prices endpoints is strictly bound to the context of the operator associated with the calling authentication token. All operations—creating, updating, or deleting airport fuel prices—apply only to the operator for which the provided token is valid.


### Get fuel prices for an airport

 - [GET /api/v2/partners/airports/{airportCode}/fuel-prices](https://developer.fl3xx.com/reference/v2/airport-fuel-prices/paths/~1api~1v2~1partners~1airports~1%7Bairportcode%7D~1fuel-prices/get.md): Retrieve all fuel prices for a specific airport that were submitted by the partner associated with the authentication token.

 Only fuel prices associated with the operator linked to the authentication token will be returned.


### Update fuel prices for an airport

 - [PUT /api/v2/partners/airports/{airportCode}/fuel-prices](https://developer.fl3xx.com/reference/v2/airport-fuel-prices/paths/~1api~1v2~1partners~1airports~1%7Bairportcode%7D~1fuel-prices/put.md): Update or set fuel prices for a specific airport. This endpoint allows partners to submit fuel pricing information that will be used for operational and financial processes.

 Only fuel prices associated with the operator linked to the authentication token can be updated.

 An operations manager needs to update the fuel price for a particular airport after receiving new rates from a provider. By using this endpoint, they can ensure that all future fuel orders and cost calculations use the most current pricing data.


### Delete all fuel prices for an airport

 - [DELETE /api/v2/partners/airports/{airportCode}/fuel-prices](https://developer.fl3xx.com/reference/v2/airport-fuel-prices/paths/~1api~1v2~1partners~1airports~1%7Bairportcode%7D~1fuel-prices/delete.md): Delete all fuel prices for a specific airport that were submitted by the partner associated with the authentication token.

 Only fuel prices associated with the operator linked to the authentication token can be deleted.

 An operations manager needs to remove all fuel prices for an airport after a provider contract ends or when prices are no longer valid. Using this endpoint ensures that no obsolete pricing data is used in future fuel orders or cost calculations.


### Delete all fuel prices

 - [DELETE /api/v2/partners/airport-fuel-prices](https://developer.fl3xx.com/reference/v2/airport-fuel-prices/paths/~1api~1v2~1partners~1airport-fuel-prices/delete.md): Delete all fuel prices submitted by the partner associated with the authentication token across all airports.

 Only fuel prices associated with the operator linked to the authentication token can be deleted in bulk.

 An operations manager needs to remove fuel prices for several airports after a system-wide update or contract changes. Using this endpoint ensures that obsolete pricing data is quickly cleared from all affected locations.


### Update individual fuel price

 - [PUT /api/v2/partners/airport-fuel-prices/{fuelPriceId}](https://developer.fl3xx.com/reference/v2/airport-fuel-prices/paths/~1api~1v2~1partners~1airport-fuel-prices~1%7Bfuelpriceid%7D/put.md): Update a specific fuel price by its ID. This endpoint allows partners to modify individual fuel pricing records.

 Only fuel prices associated with the operator linked to the authentication token can be updated.


### Delete individual fuel price

 - [DELETE /api/v2/partners/airport-fuel-prices/{fuelPriceId}](https://developer.fl3xx.com/reference/v2/airport-fuel-prices/paths/~1api~1v2~1partners~1airport-fuel-prices~1%7Bfuelpriceid%7D/delete.md): Delete a specific fuel price by its ID. This endpoint allows partners to remove individual fuel pricing records.

 Only fuel prices associated with the operator linked to the authentication token can be deleted.


## Webhooks

Manage webhook subscriptions for near real-time event notifications. These endpoints enable partners to create, manage, and monitor webhook subscriptions for receiving flight-related events and updates.

**Business Value**
- Receive near real-time notifications for flight events and updates.
- Automate integration workflows with external systems.
- Monitor flight operations and passenger changes in near real-time.
- Reduce polling overhead by using event-driven architecture.

<br/>

**Use Cases**
- Subscribe to flight updates to sync data with external booking systems.
- Monitor passenger count changes for catering and ground service coordination.
- Track aircraft changes for maintenance and operational planning.
- Receive notifications for flight cancellations and time updates.

<br/>

**Available Event Types:**
- `FLIGHT_CREATE`: New flight creation
- `FLIGHT_CANCEL`: Flight cancellation
- `FLIGHT_TIME_UPDATE`: Flight time changes
- `FLIGHT_AIRCRAFT_UPDATE`: Aircraft assignment changes
- `FLIGHT_AIRPORT_UPDATE`: Airport(s) changes
- `FLIGHT_POST_FLIGHT_STATUS`: Post-flight status updates
- `FLIGHT_MOVEMENT_UPDATE`: Flight movement updates
- `FLIGHT_PAX_COUNT_UPDATE`: Passenger count changes
- `FLIGHT_PAX_LIST_UPDATE`: Passenger list changes (e.g. new passengers, updated list, passenger document changes, etc.)


### Get webhook subscriptions

 - [GET /api/v2/webhooks/subscriptions](https://developer.fl3xx.com/reference/v2/webhooks/getwebhooksubscriptions.md): Retrieve all webhook subscriptions for the authenticated partner and operator.


- Returns all active and inactive webhook subscriptions
- Filtered by partner and operator context


### Create a new webhook subscription

 - [POST /api/v2/webhooks/subscriptions](https://developer.fl3xx.com/reference/v2/webhooks/createwebhooksubscription.md): Create a new webhook subscription for receiving near real-time event notifications.


- Validates callback URL format, only https is supported
- Sets automatic expiration date (1 month) for subscriptions

 An operations manager needs to receive near real-time notifications when flight times change. By creating a webhook subscription for  events, they can automatically sync flight data with external systems.


### Get webhook subscription by ID

 - [GET /api/v2/webhooks/subscriptions/{subscriptionId}](https://developer.fl3xx.com/reference/v2/webhooks/getwebhooksubscriptionbyid.md): Retrieve a specific webhook subscription by its unique identifier.


- Returns detailed subscription information


### Update webhook subscription callback URL or status

 - [PATCH /api/v2/webhooks/subscriptions/{subscriptionId}](https://developer.fl3xx.com/reference/v2/webhooks/updatewebhooksubscription.md): Update the callback URL for an existing webhook subscription.


- Validates new callback URL format, only https is supported
- Updates subscription status to active or inactive

 An operations manager needs to change the webhook endpoint URL after migrating to a new server. Using this endpoint, they can update the callback URL without recreating the entire subscription.


### Delete a webhook subscription

 - [DELETE /api/v2/webhooks/subscriptions/{subscriptionId}](https://developer.fl3xx.com/reference/v2/webhooks/deletewebhooksubscription.md): Delete a webhook subscription and stop receiving notifications for the associated event type.


- Immediately stops webhook deliveries

 An operations manager needs to stop receiving flight update notifications after completing a system migration. Using this endpoint, they can cleanly remove the webhook subscription.


### Renew a webhook subscription

 - [POST /api/v2/webhooks/subscriptions/{subscriptionId}/renewals](https://developer.fl3xx.com/reference/v2/webhooks/renewwebhooksubscription.md): Renew an existing webhook subscription to extend its expiration date.


- Extends subscription expiration by 1 month from current expiration date.
- Subscriptions can only be renewed 5 days before expiration.

 An operations manager wants to continue receiving webhook notifications for an existing subscription. Using this endpoint, they can extend the subscription without recreating it.


### Get webhook deliveries

 - [GET /api/v2/webhooks/deliveries](https://developer.fl3xx.com/reference/v2/webhooks/getwebhookdeliveries.md): Retrieve paginated webhook delivery history for the authenticated partner and operator.




- Returns paginated delivery history with filtering and sorting
- Supports filtering by issue date and status
- Default sorting by issue date (descending)
 
 An operations manager needs to monitor webhook delivery to troubleshoot failed deliveries. Using this endpoint, they can review delivery history and identify patterns in webhook failures.