Skip to main content

Airport Search filter upon Origin Selection

Feature Request

When searching flights departing from DFW (Dallas Fort Worth), the first few selections I get include LGW and a slew of US domestic destinations, including JFK, SFO, and ATL. I’d argue that most reward redemptions being searched/tracked aren’t short domestic hops, rather longer international redemptions like DFW-HND, JFK-HND, JFK-LHR, ORD-LHR, etc. Can a filter be placed as soon as the origin is selected to filter only for non-stop destinations, preferably prioritizing the list for international destinations?

Posted by everest ·
1 comment

Comments1

  • Dom Clark

    Team•

    Aug 4, 2025

    Sorry for the slow reply on this ticket.

    This is a really nice suggestion, but we will need to take this as a longer term goal I’m afraid. We currently fetch schedule data from our GDS and there’s too much latency involved with our current approach to offer a dynamic search solution like you’re suggesting.

    With that said, we are exploring a partnership with a few other data providers that would make this possible - we’ll keep you posted on how we progress.