TravelCaster API - Flights

The TravelCaster API provides third party systems to interact with a TravelCaster customer by accessing flight fares and booking capabilities through an easy-to-implement gateway. This readme describes the process of connecting to the API and the flows that could be implemented.

Accessing the TravelCaster API

To connect to the 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.

Shopping flow

Implementing the shopping flow, you will be able to:

• Get in one service request a combination of the cheapest flight fares options in a normalized way.
• Get Ancillary options for a selected flight option.
• Get fare options (UpSell by Brand) options for a selected flight option.
• Book a reservation.

For more information, see the Shopping flow section.

Seats flow

This flow allows you to manage seat selection and reservation. Depending on the provider's capabilities, seats can be booked during the initial booking process or as a post-booking service before ticketing. It includes:

• Retrieving real-time seat maps with availability and pricing.
• Selecting and assigning specific seats for passengers and segments.
• Managing seat status (Confirmed, Requested, or Not Added).

For more information, see the Seats flow section.

Ticketing flow

We offer two alternatives for ticketing process:

• Robotic ticketing: Applying the knowledge we have of our Providers, we implement a logic that process automated and controlled retries. It allows us to offer you a high success rate.
• Ticketing on demand: This is a standard issue ticket transaction, that returns the provider response (success or error) without applying any logic from our side.

For more information, see the Ticketing flow section.

Cancellation flow

This section describes the alternatives for cancelling the itinerary and voiding the tickets.

For more information, see the Cancellation flow section.

Fulfillment flow

On API 1.7 you can search for exchange and refund alternatives for your bookings.

For more information, see the Fulfillment API section.

Importing external bookings

If a booking was made directly with a GDS or provider outside of the TravelCaster booking flow, you can import it into TravelCaster using the ImportExternalBooking operation. This makes the booking available for retrieval and management through the standard API.

Transaction permissions

Each API user may be assigned one or more roles that restrict which operations they are allowed to call. When no roles are assigned, the user retains unrestricted access to all operations (legacy behaviour).

When roles are assigned, each operation requires at least one matching role. Calling an operation without the required role returns error 1205. Calling an operation that is not covered by any role at all returns error 1204.

Contact your TravelCaster partner to request changes to your user's role configuration.

Transactions list

This section contains information about all transactions.

For more information, see the Transactions list section.

Types of gateway to the TravelCaster API

You can access the API through JSON or XML. Check the Samples page for more information.

Certification process

After you have developed your connector for the TravelCaster API, you will have to go through a certification process to check that your requests interact correctly with the API. That process includes performing several bookings with different scenarios, request ticketing or cancellation and retrieve notifications.

For more information, see the Certification process section.

Versioning

TravelCasterAPI provides gateway versioning through its URL.

Check the URL provided in your credentials document.

This means you can switch the endpoint URL and change the version of the API you are using. Any major change in the API flow and/or returning objects will drive to a new version, which will be deployed simultaneously with the production version at the time for you to adapt your developments with the proper scheduling and planning. The API will keep three versions at any time:

• a stable production-bound version
• a beta development-oriented version, so you can adapt your development with time
• a legacy version, so you can keep connected while you catch up with our latest changes

API versions