canonical: https://jentic.com/apis/lufthansa.com/lh-partner-api

# Lufthansa LH Partner API

The LH Partner API exposes Lufthansa's partner-only flight commerce surface, covering fare search, deep links into the Lufthansa booking flow, order retrieval, baggage tracking, and pre-flight auto check-in. It is intended for travel agencies, tour operators, and approved redistributors who hold a partner agreement with Lufthansa Group. Authentication uses OAuth 2.0 client credentials against the Lufthansa partner token endpoint, and operations span 16 endpoints covering fares, OND routing, promotions, orders, baggage, and pre-flight services.

## For AI agents

Search Lufthansa partner fares, retrieve booked orders, track baggage, and trigger pre-flight auto check-in for an issued ticket number.

## Scope

Does not handle hotel booking, car rental, payment capture, or the actual ticketing transaction - use for Lufthansa partner fare search, deep-linking, order retrieval, baggage lookup, and pre-flight check-in only.

## Capabilities

- Search the lowest, best, and full-fare offers between origin and destination pairs for Lufthansa Group flights
- Generate deep links into the Lufthansa.com booking flow, including frequent-flyer (FFP) and ITCO variants
- Retrieve a booked order by orderID and passenger surname for itinerary lookup
- Look up baggage trip and contact information for a given baggage searchID
- Trigger auto check-in on a ticket number ahead of departure
- Pull origin-destination route status, top OND pairs, and current promotional price offers

## Use cases

### Partner fare shopping and deep-linking

Travel agencies and meta-search partners use the fares endpoints to surface Lufthansa Group prices alongside other carriers, then hand off to the Lufthansa.com booking flow via a generated deep link rather than rebuilding the full booking funnel. The `/offers/fares` endpoints return all-fares, best-fares, and lowest-fares variants, and `/offers/fares/deeplink` (plus FFP and ITCO variants) constructs the redirect URL with partner tracking attached. This avoids holding PCI scope while still earning partner attribution.

Example prompt: Call `/offers/fares/lowestfares` for FRA to JFK on 2026-09-15 and return the cheapest fare plus a deep link to complete the booking on lufthansa.com.

### Post-booking baggage and order servicing

After a partner-issued booking, agents need to service the passenger without rebooking through the contact centre. The `/orders/orders/{orderID}/{name}` endpoint retrieves the current order state, and `/baggage/baggagetripandcontact/{searchID}` returns the trip and contact data tied to a baggage tag - useful for chat-based travel assistants handling delayed-bag enquiries. The `/preflight/autocheckin/{ticketnumber}` endpoint can opt the passenger into automatic check-in for the trip.

Example prompt: Look up baggage record AB123456 via `/baggage/baggagetripandcontact/{searchID}` and return the trip itinerary plus the registered contact email.

### Agent-driven Lufthansa partner integration via Jentic

An AI travel concierge needs to expose Lufthansa fares and booking actions without managing OAuth client credential rotation, partner-only base URL routing, or the difference between the partner and public Lufthansa APIs. Jentic stores the OAuth client credentials in your Jentic One instance, exchanges them for short-lived tokens at call time, and exposes each operation under a stable schema the agent can call by intent.

Example prompt: Search Jentic for 'find lufthansa partner fares', load the lowestfares operation schema, and execute it for FRA to LHR on 2026-10-01.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/offers/fares/lowestfares` | Lowest fares for a given OND and date |
| GET | `/offers/fares/bestfares` | Best fares for a given OND |
| GET | `/offers/fares/deeplink` | Generate a deep link into the Lufthansa booking flow |
| GET | `/orders/orders/{orderID}/{name}` | Retrieve a booked order by ID and surname |
| GET | `/baggage/baggagetripandcontact/{searchID}` | Look up baggage trip and contact data |
| PUT | `/preflight/autocheckin/{ticketnumber}` | Enable auto check-in for a ticket |
| GET | `/promotions/priceoffers/flights/ond/{origin}/{destination}` | Promotional price offers between two airports |

## Key resources

- **Fares** — All-fares, best-fares, lowest-fares, deep links (including FFP and ITCO), and fares subscriptions
- **OND (Origin-Destination)** — Route lookup, OND status, and top OND pairs for a market
- **Orders** — Retrieve a booked partner order by orderID and surname
- **Baggage** — Baggage trip and contact lookup by searchID
- **Preflight** — Auto check-in trigger keyed off a ticket number
- **Promotions** — Price offers between origin and destination airports

## Why Jentic

- **Setup:** Wiring the LH Partner API by hand means running its client-credentials OAuth flow against the Lufthansa token URL, refreshing the bearer token before it expires, and handling the partner portal's rate limits yourself. Through Jentic you install once, import the LH Partner API from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** You choose which LH Partner operations the agent may call, so you can limit it to the ones it needs, such as searching lowest fares or retrieving an order, and leave out state changes like enabling auto check-in unless you add them. The agent only reaches the operations in the set you allow.
- **Credential handling:** Your LH Partner 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.
- **Discovery method:** Agents search Jentic by intent such as 'find lowest Lufthansa fares' or 'retrieve a booked order by surname', and Jentic returns the matching LH Partner operation with its parameter schema so the agent calls the right endpoint without browsing the Lufthansa partner portal.

## Related APIs

- **LH Public API** — Lufthansa's public surface for flight status, schedules, seat maps, and reference data
- **Amadeus Airport & City Search** — GDS-backed airport and city lookup that pairs well with Lufthansa OND search

## FAQ

### What authentication does the LH Partner API use?

The LH Partner API uses OAuth 2.0 client credentials. Partners exchange a clientId and clientSecret at https://api.lufthansa.com/v1/partners/oauth/token for a short-lived bearer token under the read:LH Open API scope. Through Jentic, the client credentials live encrypted in your Jentic One instance and tokens are minted per call, so agents never see the raw secret.

### Can I create a new booking with the LH Partner API?

Not directly. The Partner API exposes fare search, deep links, order retrieval, baggage, and pre-flight check-in but does not include a create-order endpoint. To complete a booking, generate a deep link via `/offers/fares/deeplink` and redirect the user to lufthansa.com to finish payment and ticketing.

### What are the rate limits for the LH Partner API?

Rate limits are not declared in the OpenAPI spec and are governed by each partner's commercial agreement with Lufthansa. Plan for per-second and daily caps and check your partner contract for the exact figures before bulk fare polling.

### How do I retrieve an existing Lufthansa order through Jentic?

Search Jentic for 'retrieve lufthansa partner order', load the GET `/orders/orders/{orderID}/{name}` operation, and execute it with the orderID and passenger surname. Jentic injects the OAuth bearer token automatically.

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

The Partner API at lufthansa.com/partner is gated by a partner OAuth client and exposes commercial features like deep links, orders, and auto check-in. The Public API at lufthansa.com/public exposes operational and reference data - flight status, schedules, seat maps, lounges, airport and aircraft references - using authorization-code OAuth instead.

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

Yes. Jentic One is self-hosted, so your own rules decide which LH Partner operations and credentials the agent can use. You can allow only what it needs, such as searching lowest fares or retrieving a booked order by surname, and leave out state changes like enabling auto check-in on a ticket number unless you add them. The agent can reach only the operations in the set you allow.