Install Jentic One Beta

Connect the LH Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LH Public API, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Flufthansa.com%2Flh-public-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flufthansa.com%2Flh-public-api" | 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 LH Public API.

Pull live flight status by flight number, route, or arrival/departure airport with a fromDateTime cursor

Retrieve schedules between two airports for a future date and time window

Render a seat map for a specific flight number, route, date, and cabin class

Look up lounge information for a given airport location code

Retrieve cargo routing between two airports and track an air waybill (AWB) shipment

GET STARTED

Start building with LH Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LH Public API for, with concrete tasks.

★ Live flight status and schedules in a travel concierge

An AI travel concierge or status board needs authoritative Lufthansa flight times, gate and terminal data, and on-the-day deviations rather than scraped third-party feeds. The /operations/flightstatus endpoints return per-flight, per-route, and per-airport status, while /operations/schedules returns the published schedule between two airports for a future date. This combination supports both same-day disruption handling and forward-looking trip planning.

Call GET /operations/flightstatus/LH400/2026-09-15 and return the scheduled and actual departure times plus the gate.

Cargo shipment tracking

Freight forwarders and operations teams use the /cargo/shipmentTracking/{aWBPrefix}-{aWBNumber} endpoint to look up the current status of an air waybill shipped on Lufthansa Cargo, and /cargo/getRoute to confirm available routings between two airports for a date and product code. This avoids polling Lufthansa Cargo's web portal and lets AI agents answer 'where is my shipment?' in chat.

Track AWB 220-12345678 via /cargo/shipmentTracking/220-12345678 and return the latest status event and location.

Reference data for travel apps

Travel apps frequently need to resolve a free-text airport, city, or aircraft code into structured metadata. The /references endpoints cover airports (including nearest by lat/long), airlines, aircraft, cities, and countries, returning canonical names and codes. This replaces shipping a static dataset and keeps the app aligned with Lufthansa's authoritative reference catalogue.

Call GET /references/airports/nearest/52.5200,13.4050 and return the three nearest airports to Berlin coordinates.

Agent-driven Lufthansa operations lookup via Jentic

An agent answering passenger questions in chat needs to mix flight status, seat map availability, and lounge access in a single conversation without juggling OAuth flows or memorising endpoint shapes. Jentic stores the OAuth credentials, exposes each Lufthansa Public operation by intent, and returns results the agent can quote directly to the passenger.

Search Jentic for 'lufthansa flight status', load the operation, and execute it for flight LH401 on today's date.

Key Endpoints

15 endpoints — the lh public api exposes lufthansa's openly available flight operations and reference data: live flight status, schedules, cargo routing and shipment tracking, lounge information, seat maps, and reference lookups for airports, aircraft, airlines, cities, and countries.

METHOD

PATH

DESCRIPTION

GET

/operations/flightstatus/{flightNumber}/{date}

Live status for a specific flight on a date

GET

/operations/flightstatus/arrivals/{airportCode}/{fromDateTime}

Arrivals board for an airport from a cursor time

GET

/operations/schedules/{origin}/{destination}/{fromDateTime}

Published schedules between two airports

GET

/offers/seatmaps/{flightNumber}/{origin}/{destination}/{date}/{cabinClass}

Seat map for a specific flight and cabin

GET

/cargo/shipmentTracking/{aWBPrefix}-{aWBNumber}

Track an air waybill

GET

/references/airports/nearest/{latitude},{longitude}

Nearest airports to a coordinate

GET

/offers/lounges/{location}

Lufthansa lounges at an airport location

GET

/operations/flightstatus/{flightNumber}/{date}

Live status for a specific flight on a date

GET

/operations/flightstatus/arrivals/{airportCode}/{fromDateTime}

Arrivals board for an airport from a cursor time

GET

/operations/schedules/{origin}/{destination}/{fromDateTime}

Published schedules between two airports

GET

/offers/seatmaps/{flightNumber}/{origin}/{destination}/{date}/{cabinClass}

Seat map for a specific flight and cabin

GET

/cargo/shipmentTracking/{aWBPrefix}-{aWBNumber}

Track an air waybill

GET

/references/airports/nearest/{latitude},{longitude}

Nearest airports to a coordinate

GET

/offers/lounges/{location}

Lufthansa lounges at an airport location

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the LH Public API by hand means running its client-credentials OAuth flow, keeping the bearer token fresh, and pacing calls across flight-status, schedule, seat-map, lounge, and cargo paths. Through Jentic you install once, import the LH Public API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

You choose which LH Public operations the agent may call, so you can limit it to the read operations it needs, such as flight status, published schedules, or seat maps, and leave out the rest. The agent only reaches the reference-data operations in the set you allow.

Credential isolation

Your LH Public client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'Lufthansa flight status', 'seat map for a cabin', or 'nearest airport to a coordinate', and Jentic returns the matching LH Public operation with its parameter schema so the agent calls the right endpoint directly.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

LH Partner API

Lufthansa's partner-only commerce API for fares, deep links, orders, and auto check-in

Switch to the Partner API once a partner agreement is in place and you need fare search, deep-link booking, or order retrieval rather than operational data.

Alternative

Amadeus Airport & City Search

Multi-carrier airport and city reference lookup

Choose Amadeus when the agent needs cross-carrier airport and city resolution rather than Lufthansa-specific reference data.

FAQs

Specific to using LH Public API through Jentic.

What authentication does the LH Public API use?

The LH Public API uses OAuth 2.0 with the authorization-code flow, with both authorizationUrl and tokenUrl at https://api.lufthansa.com/v1/oauth/token under the read:LH Open API scope. Through Jentic, the client credentials and authorization tokens are stored in your Jentic One instance and refreshed automatically.

Can I track cargo shipments with the LH Public API?

Yes. Call GET /cargo/shipmentTracking/{aWBPrefix}-{aWBNumber} with the air waybill prefix and number to return the latest tracking events. Use /cargo/getRoute/{origin}-{destination}/{fromDate}/{productCode} first if you also need to confirm the routing for that shipment.

What are the rate limits for the LH Public API?

Concrete rate limits are not declared in the OpenAPI spec. Lufthansa applies per-application caps once you register at the developer portal - design clients to back off on 429 responses and avoid polling /operations/flightstatus more aggressively than once per minute per flight.

How do I retrieve a seat map through Jentic?

Search Jentic for 'lufthansa seat map', load the GET /offers/seatmaps/{flightNumber}/{origin}/{destination}/{date}/{cabinClass} operation, and execute it with the flight number, route, date, and cabin class. The OAuth token is injected automatically.

Does the LH Public API include booking or order management?

No. Booking, fares, deep links, and order retrieval live in the partner-gated LH Partner API, not in this Public API. Use the Public API for operational data (status, schedules, seat maps, lounges) and reference lookups.

Can I limit what my agent is allowed to do with the LH Public API?

Yes. Because your Jentic One instance is self-hosted, you decide which LH Public operations the agent may call, so you can allow just the read endpoints it needs, such as flight status, published schedules, or seat maps, and leave the rest out. The agent only reaches reference-data lookups like airport, aircraft, and city codes if you include them in the allowed set, and it can call cargo shipment tracking only when you permit it. Your own rules govern which operations and stored credentials the agent may use at execution time.

Lufthansa LH Public API

Browse all Lufthansa APIs

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceShipping Logisticsoauth215 EndpointsREST

For Agents

Look up live Lufthansa flight status, schedules, seat maps, lounge details, cargo routing, and airline reference data such as airports, aircraft, and city codes.

Use for: I need to check the live status of LH400 today, Find all Lufthansa departures from FRA in the next two hours, Retrieve the seat map for LH401 in business class on the day of travel, List Lufthansa lounges available at FRA Terminal 1

Not supported: Does not handle bookings, ticket issuance, payment, or partner fare deep-linking - use for Lufthansa flight status, schedules, seat maps, lounges, cargo tracking, and reference data only.

The LH Public API exposes Lufthansa's openly available flight operations and reference data: live flight status, schedules, cargo routing and shipment tracking, lounge information, seat maps, and reference lookups for airports, aircraft, airlines, cities, and countries. It is the operational counterpart to the partner-only commerce API and uses OAuth 2.0 authorization-code flow against api.lufthansa.com. The 15 endpoints make it suitable for travel apps, status dashboards, and AI travel concierges that need authoritative airline data.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

53%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

67%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LH Public API to your agent

Capabilities

Start building with LH Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Lufthansa LH Public API

Jentic AI Readiness Score

LH Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness