TravelCaster API - Flights - IssueBooking operation

Back to Flights home.

You can execute this transaction to issue a booking synchronously. Please contact your TravelCaster partner if you need them to enable this issuing flow.

To issue the booking on demand, you should check first (using the RetrieveBooking operation), the status of the bookings. Only BookingStatus = 1 (confirmed) is enabled for the issuing flow.

After the issuing transaction we always recommend to execute a RetrieveBooking operation transaction to check for the following:

  • BookingStatus = 7 (Issued)
  • AirlineRecLoc and ETK for each passenger.

The presence of both informations can assert for a successful ticketing flow.

Request

JSON

http://endpoint/api/version/FlightService.json/IssueBooking [POST]

url-encoded parameter: IssueBooking([request])

returns: IssueBookingResponse

WebService

http://endpoint/api/version/FlightService.asmx

operation: IssueBooking

parameters: booking ([request])

returns: IssueBookingResponse

Structure of the IssueBookingRequest object

 IssueBookingRequest
 |_ Token
 |_ TransactionID
 |_ BookingNumber (string)

Structure of the IssueBookingResponse object

 RetrieveBookingResponse
 |_ Token
 |_ TransactionID
 |
 |_ BookingNumber
 |_ TicketNumbers (string[] - in format 000-1234567890)

Notes

For test purposes, you can send:

  • BookingNumber: "XXXXX1", and you will receive a simulated response OK.
  • BookingNumber: "XXXXX2", and you will receive a simulated response with ERROR.

Back to Flights home.

See change history for this file
Loading...