canonical: https://jentic.com/apis/lufthansa.com

# Lufthansa APIs

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.

## For AI agents

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.

## Scope

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

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| LH Partner API | e-commerce | 16 | Search Lufthansa partner fares, retrieve booked orders, track baggage, and trigger pre-flight auto check-in for an issued ticket number. |
| LH Public API | e-commerce | 15 | Look up live Lufthansa flight status, schedules, seat maps, lounge details, cargo routing, and airline reference data such as airports, aircraft, and city codes. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Live flight status, schedules, seat maps, lounges, cargo tracking, or airport and aircraft reference data | public | 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 | partner | 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 | public | The seat-map operation lives on the Public API, not the Partner API, even though both touch fares and offers. |

## Cross-API use cases

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

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

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related vendors

- **Amadeus** — GDS-backed flight, fare, and airport reference APIs that resolve cities to IATA codes and offer cross-carrier search alongside Lufthansa's own data.
- **Aviationstack** — Multi-airline real-time flight status and schedule data for agents that need coverage beyond Lufthansa Group carriers.
- **FlightAware** — Cross-carrier flight tracking and status feeds that complement Lufthansa's per-flight operations lookups.

## FAQ

### 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?

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.