Airport Gap API

Name: Airport Gap API API
Brand: Airport Gap API
Availability: InStock

★ Only Publicly Available SpecData EnrichmentAddress Validationbearer10 EndpointsREST

For Agents

List airports, calculate distance between any two airports by IATA code, and manage a per-user favourites list.

Quickstart

Get started with Airport Gap API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"calculate distance between two airports"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Airport Gap API API.

List all airports with pagination via GET /airports

Look up a specific airport by IATA code via GET /airports/{id}

Calculate the distance in km, miles, and nautical miles between two airports via POST /airports/distance

Issue a bearer token via POST /tokens for authenticated favourites operations

GET STARTED

Start building with Airport Gap API API

Explore with Jentic

View OpenAPI Spec

Use for: I want to calculate the distance between two airports, List all airports in the catalogue with pagination, Get a specific airport by its IATA code, Add an airport to my favourites list

Not supported: Does not handle flight schedules, live tracking, ticket pricing, or fuel-burn calculations — use for airport lookup, distance, and per-user favourites only.

Jentic publishes the only available OpenAPI specification for Airport Gap API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Airport Gap API, keeping it validated and agent-ready. Airport Gap is a developer-friendly REST API for accessing global airport data, calculating distances between any two airports, and managing a list of favourite airports under an authenticated user. The 10 endpoints cover paginated airport listing, lookup by IATA code, distance calculation, token issuance, and full CRUD on favourites. Designed for testing, prototyping, and educational use.

Use Cases

Patterns agents use Airport Gap API API for, with concrete tasks.

★ Airport-to-Airport Distance Calculation

Calculate the great-circle distance between any two airports given their IATA codes. POST /airports/distance accepts a JSON body with from and to fields and returns kilometres, miles, and nautical miles. Useful for travel-itinerary previews, fuel-burn estimators, and carbon-footprint calculators.

Calculate the distance between IATA codes 'KIX' and 'SFO' and return kilometres, miles, and nautical miles

Airport Catalogue Browsing

Page through the global airport catalogue using GET /airports with cursor-based pagination, or fetch a single record by IATA code with GET /airports/{id}. Suitable for populating dropdowns, building airport directories, or seeding a local cache for offline use.

Fetch the first page of airports and return the IATA codes and city names of all entries

Per-User Favourites Management

Persist a per-user list of favourite airports with optional notes by issuing a bearer token via POST /tokens, then calling the /favorites endpoints with the token. Supports add, list, update note, delete by id, and clear-all operations. Ideal for user accounts in travel-tracking or flight-comparison apps.

Authenticate with the user's email and password, add IATA 'JFK' to favourites with note 'home airport', and list all favourites

Agent Distance Lookup via Jentic

An itinerary or carbon-footprint agent searches Jentic for the distance operation, loads the schema, and executes against Airport Gap with a bearer token managed by Jentic. Avoids the need to read Airport Gap docs at runtime.

Search Jentic for 'calculate distance between two airports', load the Airport Gap operation, and call it with from='LHR' and to='SFO'

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for airport gap api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/airports

List airports with pagination

GET

/airports/{id}

Look up an airport by IATA code

POST

/airports/distance

Calculate distance between two airports

POST

/tokens

Issue a bearer token for authenticated calls

GET

/favorites

List the user's favourite airports

POST

/favorites

Add an airport to favourites

PATCH

/favorites/{id}

Update a favourite's note

DELETE

/favorites/{id}

Delete a favourite

GET

/airports

List airports with pagination

GET

/airports/{id}

Look up an airport by IATA code

POST

/airports/distance

Calculate distance between two airports

POST

/tokens

Issue a bearer token for authenticated calls

GET

/favorites

List the user's favourite airports

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Airport Gap bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped runtime tokens and the Authorization header is injected at execution time so user credentials never enter the agent context.

Intent-based discovery

Agents search by intent ('calculate distance between airports', 'add to favourites') and Jentic returns the matching operation with its body or path schema.

Time to first call

Direct integration: 2-4 hours including token flow and favourites schema. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Airport Data API

Free no-auth airport lookup without distance calculation or favourites

Choose Airport Data when you only need lookup and want zero credential overhead; choose Airport Gap when distance or favourites are required

Alternative

Amadeus Airport & City Search

Production-grade airport and city search backed by GDS data

Use Amadeus for production travel apps requiring SLAs; use Airport Gap for prototyping and learning

Complementary

Flightradar24

Live flight tracking that pairs with airport lookup and distance data

Add Flightradar24 when the agent needs live departure/arrival data on top of static airport records

FAQs

Specific to using Airport Gap API API through Jentic.

Why is there no official OpenAPI spec for Airport Gap API?

Airport Gap does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Airport Gap API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Airport Gap API use?

Airport Gap uses bearer tokens. Issue a token via POST /tokens with email and password, then pass it in the Authorization: Bearer <token> header on /favorites endpoints. Public read endpoints like /airports do not require auth. Jentic stores the token in the credential vault.

Can I calculate the distance between two airports?

Yes. POST /airports/distance with a JSON body containing from and to IATA codes returns the great-circle distance in kilometres, miles, and nautical miles in a single response.

What are the rate limits for the Airport Gap API?

Airport Gap is intended primarily for testing and prototyping. The service does not publish a hard numeric limit but applies fair-use throttling. Treat HTTP 429 responses as a backoff signal.

How do I add an airport to favourites through Jentic?

Install with pip install jentic, search for 'add an airport to favourites', load the POST /favorites operation, and execute with the airport_id. Jentic injects the bearer token at execution time.

Is the Airport Gap API free to use?

Yes. The API is free for development and testing. Read endpoints are open; favourites endpoints require an account-issued token. There is no paid tier required for typical usage.