Incomplete Flight Search API - Poll with a Session Token

Continue a previously started flight search by passing its returned sessionToken as the required sessionId query parameter. Keep currency and countryCode consistent with the original request. The tested initial flight search produced RESULT_STATUS_INCOMPLETE with usable itineraries and a nonempty token; this polling operation itself has not been independently verified, so no final-result schema, completion count or session lifetime is guaranteed. Inspect the actual response before merging additional results, deduplicate itineraries when their identifiers are available, and stop polling on explicit completion or an application-selected timeout. Session values are transient request context: obtain one from your own search, keep it private and never hard-code a captured value into public examples.

API Features

Returned-token continuation The sessionId input consumes the sessionToken returned by the initial flight search; an unrelated account or browser session is not a substitute.

Search-context currency alignment Retain the original search currency and countryCode so continuation results are not inadvertently compared under different request settings.

Application-bounded polling Choose your own backoff, request limit and timeout instead of assuming an undocumented completion interval or session lifetime.

Incremental result reconciliation Inspect each follow-up payload and merge only usable additional itineraries, preserving a partial state until completion is actually established.

Live API Demo

GET /api/project/skyscanner/flights-search-incomplete

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/flights-search-incomplete?key=<API_KEY>&sessionId=<sessionId>&currency=USD&countryCode=US'

curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/flights-search-incomplete?key=<API_KEY>&sessionId=<sessionId>&currency=USD&countryCode=US'

📢

Need Help?

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

Use Cases

Keep a loading state beside the first flight offers while your application explicitly requests further results from the same search session.
Deduplicate follow-up itineraries by returned identity before extending a travel-comparison shortlist.
Stop background continuation after an application-defined deadline and label remaining results partial instead of looping indefinitely.
Offer a deliberate refresh action for an incomplete search, starting a fresh route search when the previous session is unavailable.

Frequently asked questions

Which parameter receives the initial search's sessionToken?

Pass sessionToken from your own authorized flight search as sessionId, keeping currency and countryCode aligned with that search. It is transient search context, not a platform API key or account login token. Keep it private and redact it from request URLs and logs.

How long should I poll, and are complete results guaranteed?

Continuation response fields, completion timing and session lifetime were not independently verified. Set application-defined backoff, maximum requests and a deadline, and deduplicate by usable itinerary identity. Mark results complete only with actual completion evidence; after a timeout, retain a partial label and start a fresh search if needed.

Related operations

Guides

View Subscription Plans →

Continue an Incomplete Flight Search