Filter examples

All filters are optional and can be combined. Read the first section before you rely on one: a filter is a request to the supplier, and the suppliers do not all honour it. The numbers on this page are a measured search (ALG to CDG, one adult, 2026-12-15, sandbox, 2026-11-01); the offers of a given day differ, the behaviour does not.

Filter reference

What is enforced

suppliers[n].filtersApplied and offers[n].filtersApplied echo the filters you asked for, for every supplier. They do not prove that the supplier applied them.

So: treat nonstop, included_airlines and excluded_airlines as reliable for the validating airline, and everything else as a hint. When a filter is a hard requirement, check the offers yourself:

• baggage: travelerPricing[n].fareDetailsBySegment[m].includedCheckedBags.quantity;
• refundability: conditions.refundBeforeDeparture.allowed (indicative);
• price: pricing.finalPrice and pricing.b2bPrice, in the agency currency;
• carriers: itinerary[n].segments[m].flight.carrierCode and operatingCarrier.

You can send included_airlines and excluded_airlines together: FX-Port takes the excluded codes out of the included list and never forwards both lists to a supplier.

Non-stop only

curl https://api.fx-port.com/api/v1/get_flights \
  -H "Authorization: Bearer fxp_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "origin": "ALG",
  "destination": "CDG",
  "departure_date": "2026-12-15",
  "cabin_class": "economy",
  "passengers": {
    "adults": 1
  },
  "nonstop": true
}'

Both suppliers honour it, and filtersApplied says "maxStops": 0. There is no filter for exactly one or two stops: read itinerary[n].stops.

Refundable only

curl https://api.fx-port.com/api/v1/get_flights \
  -H "Authorization: Bearer fxp_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "origin": "ALG",
  "destination": "CDG",
  "departure_date": "2026-12-15",
  "cabin_class": "economy",
  "passengers": {
    "adults": 1
  },
  "refundable": true
}'

Checked baggage

curl https://api.fx-port.com/api/v1/get_flights \
  -H "Authorization: Bearer fxp_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "origin": "ALG",
  "destination": "CDG",
  "departure_date": "2026-12-15",
  "return_date": "2026-12-22",
  "cabin_class": "economy",
  "passengers": {
    "adults": 1
  },
  "checked_bags": true
}'

Amadeus Algeria applies the filter at the supplier. Duffel ignores it: with checked_bags: true its response had 92 offers and 24 of them had travelerPricing[n].fareDetailsBySegment[m].includedCheckedBags.quantity equal to 0, and filtersApplied.checkedBagsOnly still said true. Check the quantity on the offers you show.

Price ceiling

max_price is accepted (a positive number; 0, an empty text and null mean no ceiling and the field is ignored, a negative or non-numeric value is 400 invalid_field_type) and echoed in filtersApplied.maxPrice, but it does not cap the results in the sandbox. It is passed to Amadeus Algeria in the supplier's currency (DZD), not your agency's, and it is never sent to Duffel. Filter on pricing.finalPrice (the traveler's price) or pricing.b2bPrice (your debit) on your side.

Include airlines (allow-list)

curl https://api.fx-port.com/api/v1/get_flights \
  -H "Authorization: Bearer fxp_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "origin": "ALG",
  "destination": "CDG",
  "departure_date": "2026-12-15",
  "cabin_class": "economy",
  "passengers": {
    "adults": 1
  },
  "included_airlines": [
    "AF",
    "AH"
  ]
}'

Amadeus Algeria restricts the search to those carriers: every offer has validatingAirline[0].code AF or AH. Duffel has no carrier filter: FX-Port keeps the offers where any marketing, operating or validating carrier of any segment matches, so an offer validated by TK or QR can come back because AH flies one leg of it. The lists also accept a comma separated text ("AF,AH") and up to 20 codes.

Exclude airlines (block-list)

curl https://api.fx-port.com/api/v1/get_flights \
  -H "Authorization: Bearer fxp_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "origin": "ALG",
  "destination": "CDG",
  "departure_date": "2026-12-15",
  "cabin_class": "economy",
  "passengers": {
    "adults": 1
  },
  "excluded_airlines": [
    "IB"
  ]
}'

None of the listed carriers is the validating airline of a returned offer. (Amadeus Algeria also never returns BA, whatever you send.)

Flexible dates across all suppliers

curl https://api.fx-port.com/api/v1/get_flights \
  -H "Authorization: Bearer fxp_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "origin": "ALG",
  "destination": "CDG",
  "departure_date": "2026-12-15",
  "return_date": "2026-12-22",
  "cabin_class": "economy",
  "passengers": {
    "adults": 1
  },
  "flexible": true
}'

Every compatible supplier still returns its regular offers under results. Only suppliers with the flexible-dates capability (Amadeus Algeria) add a flexPrices key to their entry; Duffel echoes filtersApplied.flexible: true and returns no matrix. Check that flexPrices is there before you read it. See Flexible-date search, and use POST /flights/flexible_search when you want the matrix only.

Country hints

from_cc and to_cc (ISO country codes) and countries take part in the choice of suppliers; see Supplier selection. Send them only if you know why.

Related

• Search flights: the request fields and the offer.
• Supplier selection.