Lufthansa APIs for AI Agents

E CommerceOrder ManagementShipping LogisticsOfficial Vendor SpecsOAuth 2.0Agent Ready

www.lufthansa.com·Developer portal → developer.lufthansa.com

Lufthansa API Catalog

2 APIs across 1 product group. All share one credential.

E Commerce2

LH Partner APISearch Lufthansa partner fares, retrieve booked orders, track baggage, and trigger pre-flight auto check-in for an issued ticket number.~16 endpoints LH Public APILook up live Lufthansa flight status, schedules, seat maps, lounge details, cargo routing, and airline reference data such as airports, aircraft, and city codes.~15 endpoints

Which Lufthansa API should I use?

I want to...	Use	Why
Live flight status, schedules, seat maps, lounges, cargo tracking, or airport and aircraft reference data	LH Public API	The Public API exposes operational and reference data under authorization-code OAuth and needs no partner agreement.
Fare search, booking deep links, order retrieval, baggage lookup, or pre-flight auto check-in	LH Partner API	These commercial features are gated behind a partner OAuth client and only available in the Partner API.
Seat map for a specific flight and cabin	LH Public API	The seat-map operation lives on the Public API, not the Partner API, even though both touch fares and offers.

Install Jentic One Beta

Connect the Lufthansa APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lufthansa APIs, 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" | 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" | 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.

Once connected, ask your agent something like: .

Why Jentic?

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

Setup

Wiring both Lufthansa APIs by hand means running two different OAuth flows against api.lufthansa.com, refreshing bearer tokens, and routing calls between the public and partner base surfaces. Through Jentic you install Jentic One once, then your agent finds and adds the LH Public and LH Partner APIs from the Jentic directory and calls their operations by intent.

Permission scoping

Your own rules decide which Lufthansa operations the agent may reach, so you can allow read lookups like flight status, schedules, and fare search while leaving out state changes such as enabling auto check-in. Public and partner operations are scoped independently, so an agent can hold only the operations you grant.

Credential isolation

FAQs

Specific to using Lufthansa APIs through Jentic.

What is the difference between the LH Partner API and the LH Public API?

The Public API exposes operational and reference data such as flight status, schedules, seat maps, lounges, cargo tracking, and airport and aircraft codes, using authorization-code OAuth that any registered developer can use. The Partner API is gated behind a Lufthansa Group partner OAuth client and adds commercial features like fare search, booking deep links, order retrieval, baggage lookup, and pre-flight auto check-in.

Do I need a Lufthansa partner agreement to use these APIs?

You need a partner agreement only for the Partner API. The Public API is openly available to registered developers for operational and reference data. If your agent only needs flight status, schedules, seat maps, or reference lookups, you can start on the Public API alone.

Can an agent complete a Lufthansa booking end to end?

No. Neither API creates a booking or captures payment. The Partner API can search fares and generate a deep link into the Lufthansa.com booking flow, but the traveller finishes payment and ticketing on lufthansa.com. The APIs cover search, servicing, and operational lookups rather than the ticketing transaction.

Does one credential cover both Lufthansa APIs?

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs2 in catalogue

Endpoints31 indexed

AuthOAuth 2.0 — 1 credential for all 2 APIs

ProvenanceOfficial OpenAPI specs

An agent can look up live Lufthansa flight status, schedules, seat maps, lounges, cargo shipments, and airport and aircraft reference data, and, with a partner agreement, search fares, generate booking deep links, retrieve orders, track baggage, and trigger pre-flight auto check-in.

Lufthansa splits its developer surface into an openly available operations API and a partner-gated commerce API, so agents can build travel and reference features on public data and add fare search, deep-link booking, and order servicing once a Lufthansa Group partner agreement is in place.

Use for: Programmatic access to Lufthansa flight status, schedules, seat maps, lounges, cargo tracking, airline reference data, and, for partners, fare search, booking deep links, order retrieval, baggage lookup, and pre-flight auto check-in

Not supported: ticket issuance, payment capture, hotel booking, car rental, order creation

Credentials: Both APIs use OAuth 2.0 against api.lufthansa.com, but the Public API uses the authorization-code flow while the Partner API uses client credentials gated by a Lufthansa Group partner agreement, so one credential does not cover both.

All 2 Lufthansa OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.

Lufthansa's developer APIs give AI agents programmatic access to the airline's flight commerce and operations surfaces. The LH Partner API covers fare search, booking deep links, order retrieval, baggage lookup, and pre-flight auto check-in for approved travel partners, while the LH Public API exposes live flight status, schedules, seat maps, lounge details, cargo shipment tracking, and airline reference data such as airport, aircraft, and city codes. Together they let an agent plan a trip, shop and deep-link partner fares, service a booking, and answer operational questions in chat, all against api.lufthansa.com.

“lufthansa flight schedules and fares for a trip”

What AI Agents Can Do with Lufthansa

Each workflow spans multiple Lufthansa APIs. Jentic routes each operation to the right API automatically.

Plan a trip on public data, then shop partner fares

An agent uses the Public API to confirm the published schedule between two airports and resolve free-text cities to airport codes, then hands off to the Partner API to return the lowest fare and a booking deep link. This keeps trip planning on openly available data and only touches the partner-gated commerce surface once the traveller is ready to book.

Example prompt:

Call the Public schedules operation for MUC to JFK next Friday, then call the Partner lowestfares operation for the same route and return the cheapest fare plus a booking deep link.

APIs used

LH Public API + LH Partner API

Post-booking servicing across operations and commerce data

After a partner-issued booking, an agent retrieves the order and any baggage record from the Partner API, then queries live flight status and the seat map from the Public API to answer the passenger's questions in one conversation. This mixes commercial order data with operational lookups without switching tools.

Example prompt:

Retrieve the order by ID and surname from the Partner API, then call the Public flight-status operation for that flight and return the gate, terminal, and current status.

APIs used

LH Partner API + LH Public API

Your separate Public and Partner OAuth credentials are stored encrypted in 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 the Jentic directory by intent such as 'lufthansa flight status' or 'find lowest lufthansa fares', and Jentic returns the matching Public or Partner operation with its parameter schema, so the agent calls the right endpoint without knowing which Lufthansa surface it lives on.

No. Both use OAuth 2.0 against api.lufthansa.com, but the Public API uses the authorization-code flow and the Partner API uses client credentials tied to a partner agreement. You configure and store a separate credential for each API.

What travel workflows can an agent build across both APIs?

An agent can plan a trip with public schedule and reference data, shop partner fares and generate a booking deep link, then service the booking after purchase by retrieving the order, checking flight status, pulling a seat map, or tracking baggage. Cargo teams can also track air waybills and confirm routings through the Public API.

Are rate limits documented for the Lufthansa APIs?

Concrete rate limits are not declared in the OpenAPI specs. Lufthansa applies per-application caps for the Public API and governs Partner API limits through each partner's commercial agreement. Design clients to back off on 429 responses and avoid aggressive polling of flight status.