Round-Trip Flight Price Calendar API

Request the documented round-trip price comparison using originSkyId, destinationSkyId and a future outbound fromDate in YYYY-MM-DD format. Optional returnFromDate supplies the start of the return-date comparison, while currency and market set the price context. The operation is intended to compare outbound/return date combinations; its actual grid structure, returned date span and quote completeness have not been independently verified. These inputs do not document arbitrary outbound or return end dates, so do not invent unsupported range controls. Inspect returned date pairs, reject return-before-departure combinations in your application, apply trip-length preferences locally and recheck the selected pair with round-trip flight search.

API Features

Outbound-return pairing The documented comparison considers combinations of departure and return dates rather than independent one-way day quotes.

Return-window starting point Optional returnFromDate supplies a return comparison start; unsupported end-date or duration parameters must not be assumed.

Local trip-length constraints After validating returned date pairs, your application can retain weekend, seven-night or other preferred stay lengths.

Round-trip quote recheck A selected date pair still needs a date-specific round-trip itinerary search before it is presented as an available flight offer.

Live API Demo

GET /api/project/skyscanner/flights-get-price-calendar-return

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/flights-get-price-calendar-return?key=<API_KEY>&originSkyId=<originSkyId>&destinationSkyId=<destinationSkyId>&fromDate=<fromDate>&currency=USD&market=US'

curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/flights-get-price-calendar-return?key=<API_KEY>&originSkyId=<originSkyId>&destinationSkyId=<destinationSkyId>&fromDate=<fromDate>&currency=USD&market=US'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Find candidate seven-night vacations by filtering usable outbound/return combinations in your application.
Compare departure and return flexibility for a weekend break without assuming the API accepts a fixed-duration filter.
Explain why shifting a return day changes a trip's quoted price after checking the actual date-pair response.
Prepare a vacation-date shortlist that excludes invalid chronology and passes the chosen pair to a subsequent round-trip flight search.

Frequently asked questions

Can I set arbitrary outbound and return end dates?

The exposed inputs are originSkyId, destinationSkyId and fromDate, with optional returnFromDate, currency and market. No outbound or return end-date inputs are documented, and arbitrary range coverage has not been confirmed. Inspect returned date pairs without inventing unsupported controls.

How do I find lower quoted seven-night or weekend combinations?

Inspect usable returned date pairs and quotes, reject return-before-departure combinations, then calculate trip length and apply seven-night or weekend preferences in your application. Recheck the chosen pair with round-trip itinerary search. The grid schema needs validation, and a quoted pair is not a guaranteed bookable fare.

Related operations

Guides

View Subscription Plans →

Compare Departure and Return Date Combinations