For more information on these, see dates. The table below shows the combinations of date specificity allowed for the outbound and inbound dates of a return search. For more information on these, see places. The table below shows the level of precision supported for the origin and destination places. The locale you want the results in (ISO locale) Retrieve the cheapest quotes from our cached prices. Returns live prices from all our suppliers for hotel deals (in the selected market). Unless you require exact prices, we recommend you start with the cache prices API. Given the large number of suppliers that we query for quotes, the Live Pricing may take up to a minute to return all the results. searchid OPTIONAL (B2B partner needn't set the value) Elasticsearch ID, for the same request, first time needn't set the value, second time can get the value from prior response, default is '' cugsegments OPTIONAL (B2B partner needn't set the value) Only v3 supports, it allows you to add special cug segments for user. Returns live prices from all our suppliers for the requested flight itinerary (in the selected market). Similar to Browse Dates but with some pre-processing on our side to output a two-dimensional array to easily display the response in calendar format. Useful to find the lowest price for a given route, over either a month or a 12 month period. Similar to Browse Quotes but with the quotes grouped by outbound and inbound date. This provides the cheapest destinations (countries, cities or airports) from our cached data. Similar to Browse Quotes but with the quotes grouped by routes. The prices come from our cached prices resulting from our users' searches. Returns the cheapest quotes that meet your query. Please don't forget to encode the token with a URL encoder to escape special characters before sending it as a value for apiKey URL parameter. _dR-ShOTX6w2SeENoXhHTsT9Z5N4UNqwReQqU_F8WkbgMDIuZx7ud7boHnngf4fT9bpPDFJh7nxB3hWsAT8x76w =Ī successful response contains a string with token value. Please note that *not* all API endpoints support short API keys. redirect) please ensure that you use your short API key (the first 16 characters of your key). When you need to make a client-side call (e.g. Do not publish them in public code repositories or add them to client-side API calls. Make sure that you are accessing the APIs through HTTPSīe careful when sharing API keys. Please refer to each endpoint for details. You must include the API key in all API requests to the server, either as a parameter in the query or the request header. Skyscanner uses API keys to allow access to the APIs. If you need more help you can find more information and answers to questions in our FAQ which we continuously update. In order to use our APIs you need to contact us to request an API key via the following form. Skyscanner Travel APIs connect you to all the data you need to build an innovative website or app.īuild tools that solve problems for millions of travellers and travel retail businesses around the world.
0 kommentar(er)
