TravelCaster API - Fulfillment

The Fulfillment service, available from API version 1.7 on, provides operations to execute flight exchanges (rebooking to different flights) and refunds for existing bookings. It acts as an integration layer between the TravelCaster API and the Change & Refund back-end service.

Authentication

All operations require a valid access token obtained from the AuthService. Pass the token in the Token field of every request.

Tokens expire after a period of inactivity. If you receive error code 1210, request a new token via GetAccessToken before retrying.

If you do not have credentials, contact your TravelCaster partner.

Exchange flow

Exchanges follow a three-step sequence that must be executed in order:

InitializeExchange
       |
       v
SearchExchangeAlternatives   ← returns RecommendationID (valid 60 min)
       |
       v
FulfillExchange              ← requires RecommendationID from previous step

1. InitializeExchange — Retrieves the current booking details (itinerary, fare, passengers) to display before starting the exchange. No changes are made.

2. SearchExchangeAlternatives — Searches for available replacement flights for the requested legs. Returns a set of exchange offers, each with pricing and itinerary alternatives. The RecommendationID in the response must be used in the next step and is valid for 60 minutes.

3. FulfillExchange — Executes the exchange for the selected offer and leg options. Requires the RecommendationID from SearchExchangeAlternatives. On success, the booking is reissued and new ticket numbers are returned.

Refund flow

Refunds follow a two-step sequence:

PreviewRefund    ← returns refund estimates, no changes
       |
       v
FulfillRefund    ← executes the refund

1. PreviewRefund — Returns refund estimates for all tickets in the booking. No changes are made. Use this to show the expected refund amounts to the user before confirming.

2. FulfillRefund — Executes the refund for all refundable tickets. Returns the refunded amounts broken down by form of payment and per ticket.

Transaction codes

All responses include TransactionCode and TransactionMessage fields. Code "0" indicates success. A non-zero code indicates an error — see the Transaction codes reference for the complete list.

In rare cases a successful operation may include a non-empty TransactionMessage alongside code "0". This indicates a warning (e.g. the backoffice notification could not be delivered) that does not affect the result of the operation.

Certification process

Before enabling production access, implementations must pass a certification process. See the Certification process section for details.