Automate AviationData.Systems Airports
HumDay reads AviationData.Systems Airports’s own published API description and derives 6 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What HumDay can read from AviationData.Systems Airports
These are the operations a schedule or a trigger can watch.
- GETCountry list. Returns a list of countries where airport data is available
/v1/country_list - GETSearch for airport by IATA code
/v1/airport/iata/{airport_iata} - GETSearch for airport by name
/v1/airport/name/{airport_name} - GETCountry airports. Returns a list of airports for a country code(ISO 3166-1 alpha-2 code)
/v1/country/code/{country_code} - GETAutocomplete airport names.
/v1/airport/autocomplete/{airport_name} - GETSearch for airports by location
/v1/airport/nearest/{result_count}/{latitude}/{longitude}
How automating AviationData.Systems Airports works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live AviationData.Systems Airports account.
- Grant access, then go live. You approve the specific AviationData.Systems Airports operations it may use — and only those.
Automate AviationData.Systems Airports with these
- ShipEngine84 operations
- eDRV57 operations
- Mercedes Benz Car Configurator24 operations
- Lufthansa LH Partner16 operations
- Wmata Rail Station Information16 operations
- Lufthansa LH Public15 operations
- Wmata Bus Route and Stop Methods12 operations
- Mon voyage pas cher.com Public11 operations
- Deutschebahn Flinkster_API_NG10 operations
- Mercedes Benz Vehicle Image8 operations
- departureboard.io6 operations
- Wmata Incidents6 operations
Categories
Questions about AviationData.Systems Airports automation
- Can HumDay connect to AviationData.Systems Airports?
- Yes. HumDay reads AviationData.Systems Airports's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 6 operations are documented.
- Do I need to write code to automate AviationData.Systems Airports?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your AviationData.Systems Airports account.
- What can HumDay do in AviationData.Systems Airports?
- 0 of the 6 documented operations change something in AviationData.Systems Airports, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my AviationData.Systems Airports account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to AviationData.Systems Airports is held behind that approval.
Where this came from
The operations above are read from a published API description for AviationData.Systems Airports at api.aviationdata.systems//swagger/docs/v1. Descriptions are the provider’s own words, not ours. Last published 2018-05-29.