I used to work for SAP Concur, not by choice but after Hipmunk got acquired by them.
Concur talked to us to use our autocomplete DB in their "new" UI because we had better results. We were using the population size of the location to sort bigger place first.
In the end it never went beyond that one call. I think they already had multiple team working on this, not necessary together (there was a big rewrite going full force with micro-service going on).
I used to work at Hipmunk, stayed until it got shot down.
SAP Concur approached us to use our auto-completion algorithm/database to power their new UI or whatever. Apparently the 2 or 3 different DB they already had for that exact use case were not good enough.
Our result were sorted by population size of the destination, The concur people could not believe it was that only that.
These fees are not necessary available in the different API use to build these aggregator websites.
The time they are, they are often stored in a blob of text that need to be parsed.
Same situation exist for cancellation policies.
Concur talked to us to use our autocomplete DB in their "new" UI because we had better results. We were using the population size of the location to sort bigger place first.
In the end it never went beyond that one call. I think they already had multiple team working on this, not necessary together (there was a big rewrite going full force with micro-service going on).