Getting a PARTNER API token
To get access to fare data please read the business instructions and register here
As with the public data LH Open API uses Oauth 2.0 to create end point tokens, that are only valid for 24h.
Only difference between the two plans is the URI!
Request URI
Code snippet: Call
POST https://api.lufthansa.com/v1/partners/oauth/token
Content-Type: application/x-www-form-urlencoded
POST Parameter | Value |
---|---|
client_id | Your client application key |
client_secret | Your client secret |
grant_type | "client_credentials" |
Request Example
Code snippet: Curl
curl "https://api.lufthansa.com/v1/partners/oauth/token" -X POST -d "client_id=28fu8yg7tx35qkqnc6jg96fy" -d "client_secret=6jc9Zj9PE2" -d "grant_type=client_credentials"
Response Structure Definition
Key | Description |
---|---|
access_token | Your new access token |
token_type | We only use bearer tokens |
expires_in | The number of seconds until this token expires |
Response Example
Code snippet: Json
{"access_token":"d8bmzggu72dy69tzkffe6vaa","token_type":"bearer","expires_in":21600}
Note that we respond with token_type "bearer" (lower case b) yet when you send us a token it must be named "Bearer" (upper case B). This is a known issue that we are working to resolve.
You can also generate a token via our API Playground page.
Docs Navigation
- Lufthansa Open API
- Getting Started
- Public API Method Details
- Flight Schedules
- Reference Data
- Offers
- Operations
- Flight Schedules
- Flight Status
- Flight Status by Route
- Flight Status at Arrival Airport
- Flight Status at Departure Airport
- Flight Status Response
- Customer Flight Information
- Customer Flight Information at Arrival Airport
- Customer Flight Information by Route
- Customer Flight Information at Departure Airport
- Customer Flight Information Response
- Notifications
- cargo
- Partner API Method Details
- FlightOps/Crew API Method Details