Flights Integration Requirements

API for querying real-time availability and pricing

We will need access to your API in order to query real-time availability and pricing. We’ve integrated a few hundreds different airline and OTA partners and should be able to work with whatever flights API you have (however a simple JSON or XML API is preferable).

We’ll send a request to your API that includes: origin and destination codes, departure dates for each leg, cabin class and a number of passengers.

Request Example for RoundTrip Search

{
  "legs": [
    {
      "departureCode": "KWI",
      "arrivalCode": "BOM",
      "outboundDate": "2018-03-09"
    },
    {
      "departureCode": "BOM",
      "arrivalCode": "KWI",
      "outboundDate": "2018-03-17"
    }
  ],
  "adultsCount": 1,
  "childrenCount": 0,
  "infantsCount": 0,
  "cabin": "economy",
  "currencyCode": "KWD",
  "locale": "ar"
}

Parameter	Description
legs	Must contain at least one Leg (oneway). A roundtrip request contains two legs. A multi-city request contains up to 6 legs.
legs / departureCode	3 letter IATA departure city/airport code (let us know if you do not support metro city codes (e.g. LON or MOW), in that case we will use airport codes when requesting your API
legs / arrivalCode	3 letter IATA arrival city/airport code
legs / outboundDate	Departure date for the leg, formatted as YYYY-mm-dd.
adultsCount	Number of Adults, 1-9
childrenCount	Number of Children, 0-9
infantsCount	Must be not more than a number of adults (let us know if you do not support search by infants)
cabin	Possible values: economy, premium_economy, business, first (let us know if you do not support any of these cabin classes)

Response Example for RoundTrip Search

{
  "flightItineraries": [
    {
      "price": {
        "currencyCode": "KWD",
        "pricePerAdult": 65,
        "pricePerChild": 0,
        "pricePerInfant": 0,
        "totalAmount": 75.375,
        "isRefundable": true
      },
      "leg1": {
        "segments": [
          {
            "cabin": "Economy",
            "flightNumber": "664",
            "airlineCode": "WY",
            "operatingAirlineCode": "WY",
            "aircraftCode": "320",
            "departureDateTime": "2018-12-14T03:55:00",
            "arrivalDateTime": "2018-12-14T07:05:00",
            "departureAirportCode": "KWI",
            "arrivalAirportCode": "MCT"
          },
          {
            "cabin": "Economy",
            "flightNumber": "203",
            "airlineCode": "WY",
            "operatingAirlineCode": "EK",
            "aircraftCode": "330",
            "departureDateTime": "2018-12-14T09:00:00",
            "arrivalDateTime": "2018-12-14T13:10:00",
            "departureAirportCode": "MCT",
            "arrivalAirportCode": "BOM"
          }
        ]
      },
      "leg2": {
        "segments": [
          {
            "cabin": "Economy",
            "flightNumber": "204",
            "airlineCode": "WY",
            "operatingAirlineCode": "WY",
            "aircraftCode": "320",
            "departureDateTime": "2018-12-19T16:15:00",
            "arrivalDateTime": "2018-12-19T17:45:00",
            "departureAirportCode": "BOM",
            "arrivalAirportCode": "MCT"
          },
          {
            "cabin": "Economy",
            "flightNumber": "647",
            "airlineCode": "WY",
            "operatingAirlineCode": "EK",
            "aircraftCode": "320",
            "departureDateTime": "2018-12-19T18:50:00",
            "arrivalDateTime": "2018-12-19T20:20:00",
            "departureAirportCode": "MCT",
            "arrivalAirportCode": "KWI"
          }
        ]
      },
      "deeplinkUrl": "https://www.yourdomain.com/booking/123456789",
      "mobileDeeplinkUrl": "https://m.yourdomain.com/booking/123456789"
    }
  ]
}

Attribute	Description
flightItineraries	An array of flight itineraries, each intinerary contains price, legs and deeplinkUrl
flightItineraries / price	Contains total price covering all passengers, price per adult, price per child, price per infant, 3-letter ISO 4217 currency code and information on whether fare is refunable or non-refundable
legs	there must be at least one leg in the response (for one-way). Two legs for roundtrip, and more than two for multi-city
legs / segments	An array of segments
legs / segments / cabin	Actual cabin class of the segment, e.g. Economy, Premium Economy, Business, or First
legs / segments / flightNumber	Flight number
legs / segments / airlineCode	2-letter IATA or 3-letter ICAO marketing airline code
legs / segments / operatingAirlineCode	2-letter IATA or 3-letter ICAO operating airline code
legs / segments / aircraftCode	Aircraft code
legs / segments / departureDateTime	Departure date time in timezone of departure airport
legs / segments / arrivalDateTime	Arrival date time in timezone of arrival airport
legs / segments / departureAirportCode	3-letter IATA departure airport code
legs / segments / arrivalAirportCode	3-letter IATA arrival airport code
deeplinkUrl	Deeplink url
mobileDeeplinkUrl	Mobile deeplink url (this attribute is required if your mobile and desktop deeplinks are different)

Languages and currencies

Please provide the complete list of language and currency codes you support.

Caching Strategy

Please advise how long results can be safely cached. Using this information, we can cache responses from your API to minimize the number of live queries sent to your API server. Our default caching time is 30 minutes.

Deeplink Construction

For each flight result we need a way to “deeplink” the user into your website directly for the specific offer. Best practices for conversion is to redirect users via the deeplink directly to the booking/summary page with the flights the user has selected on the Wego website.

Ideally a Booking/Deeplink URL is to be provided in each flightItinerary in your API response. Any required affiliate tag or tracking parameters should be included in the deeplink URL.

If you are not able to include deeplink URL into the API response, please provide us with an example of the deeplink URL. If your mobile and desktop deeplinks are different, both desktop and mobile deeplink URL examples should be provided.

Please advise if you require us to add any tracking parameters to our deeplinks in order for you to track referrals from Wego in your reporting systems. Please refer to Conversion tracking for more information on tracking.

Supported Routes

If you have route-related limitations, please provide us with a list of routes you wish to be sent searches for, so that we will avoid sending unnecessary requests to your API. It should be a list of Origin and Destination pairs, values can include 3-letter city/airport codes (eg SHA) or 2-letter country codes (eg CN).

Payment Charges

Please provide us with the list of payment methods you support along with the respective payment charges. The charges can be fixed or a percentage of total booking amount. If the charges are dynamic, they must be provided in each flightItinerary in your API response.

Partner Logo

Please provide us with logo in .png format, size 200x70, it will be displayed on the search results.

If you want your logo to be displayed in the "Parners" section on the Wego homepage, please reach out to your Wego account manager (note that we make decisions on case to case basis).

Wego IP Addresses

Please whitelist our IP addresses:

To get started, once you have signed a Commercial Agreement with Wego, please send your API documentation and login details to your Wego Account manager.

API for querying real-time availability and pricing​

Request Example for RoundTrip Search​

Response Example for RoundTrip Search​

Languages and currencies​

Caching Strategy​

Deeplink Construction​

Supported Routes​

Payment Charges​

Partner Logo​

Wego IP Addresses​