Skip to main content

Advanced Calendar Search

1.9.5.1
Air
Search
REST API
Try now

What is it?

In detail: the API uses the Travel Insight engine to retrieve up to 192 days of shopped fare data for a given city pair and length of stay available in the SabreĀ® cache. The API returns up to 200 lead fares (either nonstop or overall, whichever is lowest) with the corresponding flight itinerary and fare breakdown for each lead fare.

Multiple search preferences are available to sort and filter results, including the ability to:

  • limit flight options to online itineraries only, include/exclude carriers and specify particular days of the week;
  • specify multiple lengths of stay, a maximum number of stops;
  • connecting-flight time or a departure/arrival time window on each flight leg.

Why use it?

Specify weekday travel dates

You could use this API to feature one way/roundtrip, weekday flight options within a given month. For example, to search for flight options that depart in February on Thursdays and Fridays departing from San Francisco to Dallas - Fort Worth, use airport code "SFO" (San Francisco International) for origin and "DFW" (Dallas/Fort Worth International) for destination. The response will be flight itineraries departing only on Thursdays and Fridays in the month of February from "SFO" to "DFW."

Define the number of options to return per date pair

You could use this API to feature a maximum number of flight options per date pair, e.g., 20 date pairs with a maximum of 10 options per date pair. The response will be the 200 most inexpensive itineraries across the date range and with no pair receiving more than 20 itineraries.

How to use?

Paginate itineraries for a given request ID with "limit" and "offset"

Paginate search results for a given request ID by specifying how many itineraries to return per request in limit and specifying the starting position to begin retrieving itineraries in offset. This allows you to more quickly retrieve and return search queries for mobile application requests. Rather than returning all itineraries, you could return 10 itineraries per request in limit (limit=10) and specify a starting position of 1 in offset (offset=1). Then you can select a starting position of 11 (offset=11) to retrieve the next 10 results (limit=10).

  1. The first request returns a Request ID for the itinerary data set and a Tag ID with each itinerary from the Advanced Calendar Search API.

POST https://[ENDPOINT]?enabletagging=true&limit=10&offset=1 HTTP/1.1

  1. The next request retrieves the cached itineraries from 11 to 20 from the Pagination Request URL.

GET https://[ENDPOINT]/[REQUESTID]?limit=10&offset=11 HTTP/1.1

  1. The last request retrieves the cached itineraries from 21 to 30 from the Pagination Request URL.

GET https://[ENDPOINT]/[REQUESTID]?limit=10&offset=21 HTTP/1.1

Retrieve a specific itinerary for a given tag ID from the Tag ID Lookup URL

  1. The first request returns a Request ID for the itinerary data set and a Tag ID with each itinerary from the Advanced Calendar Search API.

POST https://[ENDPOINT]?enabletagging=true HTTP/1.1

  1. The next request retrieves an itinerary from the Tag ID Lookup URL.

GET https://[ENDPOINT]/tags/[TAGID] HTTP/1.1