Airports Lookup API + Webhooks Integration

Why connect them

The Airports Lookup API in Webhooks.

Webhooks enable real-time communication between any systems. Connecting APIs with webhooks creates unlimited integration possibilities. Build custom workflows that respond instantly to events from any source.

What you can build

Workflows worth wiring.

Receive data from any system and enrich it with API calls before processing

Build custom notification systems that validate and route incoming data

Create middleware that transforms and validates webhook payloads

Chain multiple APIs together for complex data processing pipelines

Templates

Ready-made ideas.

Incoming webhook with IATA code Fetch airport lookup → return iata, icao, name, city, country, and tz via webhook response

Airport Lookup Webhook Service

Build an airport data microservice that returns full airport details via webhook integration.

Incoming webhook with booking data Fetch airport lookup for route codes → return name, city, and tz for departure and arrival via webhook

Travel Booking Webhook Enrichment

Enrich travel booking webhooks with departure and arrival airport names, cities, and timezones.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with Webhooks as the trigger app and "Receive webhook" 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 Webhooks action for "Send webhook" 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 Webhooks module set to "Receive webhook". 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 Webhooks module for "Send webhook". 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 Webhooks trigger node for "Receive webhook" 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 Webhooks node for "Send webhook" 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 Webhooks receives.

icao"KMCI"

iata"MCI"

name"Kansas City International Airport"

city"Kansas City"

state"Missouri"

country"US"

Airports Lookup API + Webhooks