Transavia Airports API v2

Name: Airports API v2 API
Brand: Airports API v2
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey5 EndpointsREST

For Agents

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

Use for: I need to all airports, I want to airport(s) by country code., Search for nearest airport(s) by geo coordinates., Find all nearest airport(s) by airport id.

Install Jentic One Beta

Connect the Airports API v2 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Airports API v2, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Airports API v2 API.

All airports

Airport(s) by country code.

Nearest airport(s) by geo coordinates.

Airport by id.

GET STARTED

Start building with Airports API v2 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Airports API v2 API for, with concrete tasks.

★ 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..

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.

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.

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

Key Endpoints

5 endpoints — returns all airports.

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.

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.

Why Jentic?

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

Credential isolation

Airports API v2 apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'all airports') and Jentic returns the matching Airports API v2 operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Airports API v2 integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Airports API v2 API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.