Sessionless and Session Tokens
This workflow demonstrates how to combine access (sessionless) and session tokens into a flight shop and book request.
The following workflow demonstrates the steps once a client begins the shopping process.
- Invoke the Create Access Token API to get a new access (sessionless) token (or use an existing access token).
- Invoke the Bargain Finder Max API with multiple concurrent calls to allow shopping different clients.
- Reuse the same access token until it expires.
The following workflow demonstrates the steps once a client proceeds with the booking process.
- Invoke the Create Session API to obtain a SOAP session token—if you have designed an in-house Connection Manager solution, invoke the connection manager and get a session from your Connection Manager, if you have not designed an in-house Connection Manager solution, create the session directly through the Create Session API.
- Use the Orchestrated Air Booking API to book one or more flight segments.
- Use the Passenger Details API to add all required information to create a passenger name record (PNR) and end the transaction.
- We recommend you clean up your sessions once your booking workflow is completed. If you are using a Connection Manager, call your Connection Manager to return the session, which should have design logic for next steps. If you’re not using a Connection Manager, you may either let the session expire or close the session via the Close Session API.
- SOAP APIs: Steps 4 and 5 can be combined into one call—book one or more flight segments and add all required information to create a passenger name record (PNR) using CreatePassengerNameRecordRQ.
- Sessionless (access) tokens returned via REST and SOAP API authentication are the same type of token and can be used interchangeably between REST and SOAP.