SkyScanner API via RapidAPI: Missing return flight data

Other Questions RapidAPI
1

I’m working on a personal project using the SkyScanner API through RapidAPI in Go. I’m trying to fetch flight info for a round trip, but the API response only includes the outbound flight details.

Here’s a snippet of the response I’m getting:

{
  "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"
  }],
  ...
}

As you can see, there’s no info about the return flight. Am I missing something in my API request? Has anyone encountered this issue before? Any tips on how to get the complete round trip data would be super helpful. Thanks in advance!

2

I’ve worked extensively with the SkyScanner API, and I can confirm that the behavior you’re experiencing is indeed by design. The API doesn’t provide round trip information in a single response. To get the complete round trip data, you’ll need to make two separate API calls: one for the outbound flight, using your departure date, and another for the inbound flight, using your return date. Then, in your application, you’ll need to combine these two responses to present the full round trip information to your users. It’s not the most intuitive approach, but it does offer more flexibility for complex itineraries. Remember to handle potential mismatches or unavailability in either direction when processing the results.

3

I’ve been working with the SkyScanner API for a long time, and I understand the frustration that comes with its design. In my experience, the API intentionally provides separate data for each leg of a round trip, meaning you need to perform distinct API calls for the outbound and inbound segments. This approach may seem cumbersome at first, but it allows for more flexibility when dealing with complex itineraries. When integrating the data in your application, I make sure to carefully merge the responses and add robust error checks so that any inconsistencies are handled gracefully.

Overall, while it requires extra work, the process becomes smoother as you get used to combining the results properly.

4

hey liam, i’ve run into this too. the skyscanner api can be tricky. for round trips, you gotta make separate requests for each leg. so do one for outbound, then another for inbound with the dates switched. its kinda annoying but thats how they set it up. hope this helps!