canonical: https://jentic.com/apis/transavia.com/airports-api-v2

# Transavia Airports API v2

Returns all airports. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically all airports, airport(s) by country code.. Covers 5 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- All airports
- Airport(s) by country code.
- Nearest airport(s) by geo coordinates.
- Airport by id.
- Monitor Airports API v2 operational status and events

## Use cases

### Developer Tools Operations

Use the Airports API v2 to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including all airports, airport(s) by country code., nearest airport(s) by geo coordinates..

Example prompt: Call GET / to all airports

### Automated countrycode Management

Automate countrycode operations by combining multiple Airports API v2 endpoints. Agents can airport(s) by country code. and then nearest airport(s) by geo coordinates. in a single workflow.

Example prompt: Call GET `/countrycode/{countryCode}` to airport(s) by country code., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Airports API v2 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'all airports', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/` | All airports |
| GET | `/countrycode/{countryCode}` | Airport(s) by country code. |
| GET | `/nearest` | Nearest airport(s) by geo coordinates. |
| GET | `/nearest/{id}` | Nearest airport(s) by airport id. |
| GET | `/{id}` | Airport by id. |

## Key resources

- **countrycode** — Operations related to countrycode
- **default** — Operations related to default
- **nearest** — Operations related to nearest

## Why Jentic

- **Setup:** Wiring the Airports API v2 by hand means passing its apikey header or subscription-key query parameter on every call to api.transavia.com and handling errors yourself. Through Jentic you install once, import the Airports API v2 from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Airports API v2 is read-only, so scope the agent to the operations it needs, such as listing airports, looking up by country code, or finding the nearest airport, and leave out anything the workflow does not require. Every operation you allow is one you have chosen.
- **Credential handling:** Your Airports API v2 key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list all airports' or 'find the nearest airport', and Jentic returns the matching Airports API v2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Airports API v2 use?

The Airports API v2 uses an API key passed in the `apikey` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I all airports with the Airports API v2?

Yes. Use the GET / endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Airports API v2?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I all airports through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'all airports'. Jentic returns the matching Airports API v2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Airports API v2 have?

The Airports API v2 exposes 5 endpoints covering countrycode, default, nearest operations.

### Can I limit what my agent is allowed to do with the Airports API v2?

Yes. Because you run Jentic One self-hosted, your own rules decide which Airports API v2 operations and which stored API key the agent may use. The API is read-only, so you can allow just the calls a workflow needs, such as listing all airports or looking up airports by country code, while withholding nearest-airport lookups by coordinates or by id. Every operation the agent can reach is one you have explicitly permitted.