TravelCaster API - Authentication
Back to API documentation.
To connect to the TravelCaster API you will need a username and a password. The API provides you with two passwords, one for the development environment and one for the production one. Depending on the password you send with your credentials, you will access one environment or the other.
If you don't have a username/password, please contact your TravelCaster partner.
Every operation you call afterwards (Flights, Fulfillment, Reports) requires a valid token obtained through the GetAccessToken operation. Pass it in the Token field of every subsequent request; the same token is echoed back in each response for conversation validation purposes.
Tokens have a limited lifetime. If a request fails with error code 1210 (session expired), request a new token before retrying.
Which GetAccessToken do I use?
Where the operation lives depends on the API version you are connecting to:
- API 1.7 and above — authentication is handled by a dedicated AuthService. See GetAccessToken.
- API 1.6 and below — authentication is part of the FlightService. See the legacy FlightService.GetAccessToken.
If you are upgrading from 1.6 to 1.7, see the migration guide for a full breakdown of what changed in the request, response and error handling.
Back to API documentation.