SkyScanner API via RapidAPI not showing return flight info

Other Questions RapidAPI
1

I’m working on a personal project using the SkyScanner API through RapidAPI in Go. I’m trying to get info for both outbound and return flights, but the API response only shows the outbound flight details.

Here’s what I’m getting in the response:

{
  "Quotes": [{
    "QuoteId": 1,
    "MinPrice": 403.0,
    "Direct": true,
    "OutboundLeg": {
      "CarrierIds": [851],
      "OriginId": 81727,
      "DestinationId": 60987,
      "DepartureDate": "2019-12-01T00:00:00"
    },
    "QuoteDateTime": "2019-11-29T14:24:00"
  }],
  "Places": [
    // ... place details ...
  ],
  "Carriers": [
    // ... carrier details ...
  ],
  "Currencies": [
    // ... currency details ...
  ]
}

As you can see, there’s no info about the return flight. Am I missing something in my API request? Has anyone else run into this issue with the SkyScanner API? Any help would be great!

2

I’ve been using the SkyScanner API for a while now, and I can confirm that getting return flight info can be tricky. Here’s what I’ve learned:

The API doesn’t give you both legs in one go; you need to make separate calls for outbound and inbound flights. It’s not ideal, but that’s how it’s designed. I make one request for the outbound flight (origin to destination) and another for the inbound flight (destination back to origin), then combine the results in my code to get the full picture. Also, be sure you’re using the correct endpoint—‘Browse Quotes’ usually provides better search results. If you’re still encountering issues, double-check your API key and parameters, as even a minor typo can lead to unexpected results. Hope this helps!

3

yo, i had the same problem with skyscanner api. turns out you gotta make TWO requests - one for outbound and one for inbound flights. it’s kinda annoying but that’s how it works. just flip the origin/destination for the return flight query and you should be good to go!

4

I’ve encountered a similar issue with the SkyScanner API via RapidAPI. The problem lies in how the API handles round-trip queries. By default, it only returns outbound flight information in the initial response.

To get return flight details, you need to make a separate API call specifically for the return leg. Use the same endpoint, but swap the origin and destination, and set the departure date to your desired return date.

Additionally, ensure you’re using the ‘Browse Quotes’ endpoint rather than ‘Browse Routes’. The former provides more comprehensive flight information, including separate quotes for outbound and inbound journeys.

If you still face issues after trying these steps, double-check your API key permissions and consider reaching out to RapidAPI support for further assistance.