β½ Publishing Airport Fuel Prices
Send your fuel prices per airport through the FL3XX API and put them in front of the operator's dispatchers, right where they plan the flight
Send Prices
Where They Appear
Maintain Prices
Limits
Fuel suppliers and fuel price providers can publish their prices to an FL3XX operator airport by airport. Every price you send lands on that airport in the operator's FL3XX environment, and from there it is pulled into the flights in Dispatch, so the dispatcher sees your offer while choosing a fuel supplier for the leg.
All examples use the test server https://test.fl3xx.com. Every request is bound to the operator linked to your token, so the prices you send are only visible to that operator. For full request and response schemas, see the API Reference.
π‘Common Use Case: A Daily Price Feed
Once a day, or whenever your prices change, send one request per airport with the full set of offers you hold there. Each request replaces what you sent for that airport before, so the operator always sees your current list, with no stale tiers left behind.
Send Prices
Publish the prices for one airport
The Endpoint
/api/v2/partners/airports/{airportCode}/fuel-pricesSet the fuel prices for one airport.
airportCode accepts an ICAO, IATA or FAA code, or the FL3XX airport id. Authenticate with the X-Api-Client-Id and X-Auth-Token headers.
The Request Body
The body is an array of price entries. Each entry describes one offer: one FBO, one contractor and one volume tier.
fboNameRequiredName of the FBO at the airportcontractorNameRequiredName of the contractor providing the fuelcurrencyRequiredEUR or USDunitRequiredLITER or GALLON_USAvolumeFromRequiredLower bound of the tier, inclusive, zero or greatervolumeToRequiredUpper bound of the tier, inclusive, zero or greaterpricingPrivateOptionalPrivate pricing, with price and priceIndexpricingCommercialOptionalCommercial pricing, with price and priceIndexpreArrivalRemarksOptionalPre arrival instructions for the fuel servicepaymentMethodOptionalAccepted payment methodsphoneOptionalContact phone of the FBO or fuel provideremailOptionalContact email of the FBO or fuel providerremarksOptionalAny additional notesexpirationDateTimeOptionalWhen the offer expires, as yyyy-MM-ddTHH:mm:ss.SSSZExample Request
curl -X PUT "https://test.fl3xx.com/api/v2/partners/airports/LOWW/fuel-prices" \
-H "X-Api-Client-Id: <your client id>" \
-H "X-Auth-Token: <your token>" \
-H "Content-Type: application/json" \
-d '[
{
"fboName": "Jet FBO",
"contractorName": "Shell Aviation",
"currency": "EUR",
"unit": "LITER",
"volumeFrom": 0,
"volumeTo": 5000,
"pricingPrivate": { "price": 1.85, "priceIndex": 105.5 },
"pricingCommercial": { "price": 1.65, "priceIndex": 98.0 },
"preArrivalRemarks": "24 hour notice required",
"paymentMethod": "Credit Card, Invoice",
"remarks": "Preferred fuel provider",
"expirationDateTime": "2026-12-31T23:59:59.000Z"
}
]'A successful call returns 200 with the stored entries, each now carrying its own id, the airport, the source and the created and updated timestamps. Keep the id if you want to change or remove a single entry later.
Where They Appear
Airports and Dispatch in FL3XX
Maintain Prices
Read, update and delete what you sent
Limits
Rules every request has to follow