Airports Lookup API + GitHub Integration

Why connect them

The Airports Lookup API in GitHub.

GitHub is where developers build software together. Connecting APIs to GitHub enables automated code workflows, intelligent issue management, and CI/CD enhancements. Supercharge your development processes with external data.

What you can build

Workflows worth wiring.

Automatically validate URLs in README files for broken links

Check DNS configurations when deploying to new environments

Verify SSL certificates as part of deployment pipelines

Create issues automatically when external monitoring detects problems

Templates

Ready-made ideas.

Scheduled weekly trigger Fetch airport lookup for tracked airports → commit iata, icao, name, and city to GitHub data repository

Airport Data Feed in GitHub

Maintain an open-source airport data feed by committing airport details to a GitHub repository.

New pull request opened in GitHub Fetch airport lookup for IATA codes in PR → comment with name and city for code review validation

Airport Code Validation in GitHub

Validate airport codes in pull requests by looking up and commenting with full airport details.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with GitHub as the trigger app and "New issue" as the event. Connect your account.
2
Add the API action. Add APIVerve as the action, select the Airports Lookup API, and map your trigger data to the request.
3
Send it back. Add a second GitHub action for "Create issue" and map the returned fields (like icao) into it.
4
Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.

Set up with Make

1
Add the trigger. Create a scenario and add a GitHub module set to "New issue". Authenticate your account.
2
Call the API. Add an HTTP module pointing at api.apiverve.com/v1/airports with your x-api-key header. Pass the trigger's data as the input.
3
Parse & map. Add a JSON module to read the response, then a GitHub module for "Create issue". Map fields like data.icao into place.
4
Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.

Set up with n8n

1
Add the trigger node. Start a workflow with a GitHub trigger node for "New issue" and connect your credentials.
2
Add an HTTP Request node. Point it at api.apiverve.com/v1/airports using Header Auth (x-api-key). Feed in the trigger data.
3
Map with expressions. Add a GitHub node for "Create issue" and reference the response with expressions such as {{ $json.data.icao }}.
4
Execute & activate. Execute manually to verify, then activate the workflow for production.

The payload

What GitHub receives.

icao"KMCI"

iata"MCI"

name"Kansas City International Airport"

city"Kansas City"

state"Missouri"

country"US"

Airports Lookup API + GitHub