// the find
amadeus4dev/amadeus-python
Python library for the Amadeus Self-Service travel APIs
Official Python SDK for Amadeus's travel APIs — flights, hotels, activities, transfers, and a handful of ML prediction endpoints (delay prediction, trip purpose, choice prediction). It's a thin wrapper that maps the REST API paths to a Python object hierarchy. Target audience is developers building travel apps or tools that need real GDS data without a direct IATA connection.
The URL-to-object mapping is clean and predictable — if you know the REST path, you can guess the Python call. OAuth token handling is automatic with built-in refresh, which saves the usual boilerplate. Pagination is a first-class concern with `.next()`/`.previous()` helpers instead of making you manage cursors manually. The test/production hostname toggle is a single param — sensible for a paid API where a wrong call costs money.
259 stars for an official SDK from a major GDS player is a red flag — either nobody's using the Python library or they're going straight to REST. The directory tree shows one file per endpoint, which means ~60 files for what's essentially the same two lines of code repeated; it's a maintenance smell waiting to happen when the API adds endpoints. No async support — every call blocks, so building anything concurrent means threading around it yourself. The analytics endpoints (most booked destinations, busiest period) use 2017 sample data in the README examples, which suggests those endpoints see minimal real-world use and may have data gaps.