The API

The Flight API comprises of a WSDL 1.1 web service, communicating using SOAP 1.2 structured requests and responses.

The WSDL to be used to generate code stubs to communicate with the API: https://testapi.travelstart.com/ts-ext-services/flight-service?wsdl . This also describes optional and mandatory fields and types for those fields. We recommend to use the WSDL to generate the stubs instead of hand-coding.

The API is session-based, and uses a generated session identifier string to maintain session (CorrelationID). This is returned in the first "search" operation response, and should be included in all subsequent requests for the session. Issuing a new search request is considered as starting a new session. This rule does not apply to the retrieve operation.

Authentication

Each message makes use of a "Source" element in the header of the message, which contains information used to authenticate the user. The integrating API user will need to populate these fields with the username / password details provided by Travelstart.

Please use the sample requests in the appendix of this document; wherever <USERNAME> is specified in the message header, replace with the alphanumeric API username provided by Travelstart. Similarly, <PASSWORD> indicates where the user must provide their password field. Together, this information is used to authenticate requests against the API.

Very important

Your username is linked to a market, so you need a separate username for each market you want to use the API against. Please see the Environments section for the API URLs to use.

Environments

Test API URL for all markets: https://betaapi.travelstart.com/ts-ext-services/flight-service

Production credentials will be provided on certification.