FastSearch - the Transfer of Parameters to the Search Form

FastSearch in Websky is a feature of the Websky online booking system that allows you to redirect users to a page with already filled in search parameters or directly to the actual search results.

Purpose

The function automatically fills in the search form and starts the search process.

Examples of usage

Generating links for banners or special offers for customers; such links will lead user to the search form with filled in search parameters: departure and destination, date, number and types of passengers and other parameters. You can also start the search process according to the set parameters.

Working principle

To use Fast Search, enable the option of the same name under settings 'Site Management → Domains and Protocols → Enable FastSearch feature (transfer of search parameters). A Fast Search request consists of parameters and their values, which are entered in a certain order in the link.

Fast Search for Frontend 1.0

Attention! The instructions below are only valid for old design themes! For design themes inherited from the wurst theme, see subsection "Fast Search for Frontend 2.0" of this article!
When using Frontend 1.0 the link looks like this:

http://SITENAME/?trip_type=OW&out_iata=MOW&in_iata=BER&departure_date=21.10.2009&adults=1&children=0&input_vendors=SU,PS&param_by_get=on

Variable names are the same as field names on the search form.

• Variable names must satisfy the constraints from the corresponding search form settings. For example, if you can search up to 270 days in advance according to the settings, this limitation will also apply to FastSearch.
• It is recommended not to include variables that suppose true as a value in your query.
• To redirect user to form with filled in search parameters, add get-param &param_by_get=on at the end of query, otherwise standard search form field presets will work.
• To send the user directly to search results, add the get-parameter '&fast_search=on.

Examples

One way route

Direct one way itinerary from Moscow to Paris for two adults with departure on 25.10.2016 Request fills out a search form http://SITENAME/?trip_type=OW&out_iata=MOW&in_iata=PAR&departure_date=25.10.2016&direct=true&adults=2&param_by_get=on Request starts the search process http://SITENAME/?trip_type=OW&out_iata=MOW&in_iata=PAR&departure_date=25.10.2016&direct=true&adults=2&param_by_get=on&fast_search=on

Round-trip route

Round-trip itinerary Moscow - Paris - Moscow in economy class for two adults and an infant Request fills in the search form http://SITENAME/?trip_type=RT&out_iata=MOW&in_iata=PAR&departure_date=25.10.2016&back_departure_date=27.10.2016&class=econom&adults=2&infants=1&param_by_get=on Request starts the search process http://SITENAME/?trip_type=RT&out_iata=MOW&in_iata=PAR&departure_date=25.10.2016&back_departure_date=27.10.2016&class=econom&adults=2&infants=1&param_by_get=on&fast_search=on

Complex route

Complex route for one adult from Moscow to Paris with departure 25.10.2016, from Paris to St. Petersburg with departure 26.10.2016, from St. Petersburg to Moscow, with departure 29.10.2016. Request fills in the search form http://SITENAME/?trip_type=CR&cr_iata[0]=MOW&cr_back_iata[0]=PAR&cr_date[0]=25.10.2016&cr_iata[1]=PAR&cr_back_iata[1]=LED&cr_date[1]=26. 10.2016&cr_iata[2]=LED&cr_back_iata[2]=MOW&cr_date[2]=29.10.2016&adults=1&param_by_get=on Request launches search process http://SITENAME/? trip_type=CR&cr_iata[0]=MOW&cr_back_iata[0]=PAR&cr_date[0]=25.10.2016&cr_iata[1]=PAR&cr_back_iata[1]=LED&cr_date[1]=26. 10.2016&cr_iata[2]=LED&cr_back_iata[2]=MOW&cr_date[2]=29.10.2016&adults=1&param_by_get=on&fast_search=on

Request Parameters

Route "One-way" or "Round trip"

Query parameters for one-way and round-trip itinerary searches
Element	Variable	Allowable values
Trip type	trip_type	OW One way RT Round trip CR Complex route
Departure point	out_iata	MOW IATA airport code
Arrival point	in_iata	LED IATA airport code
Departure date	departure_date	- 10/25/2013 Date in the format dd.mm.yyyy
Date of return flight	back_departure_date	- 10/27/2013 Date in the format dd.mm.yyyy
Departure time	prefered_departure_type	width="80" |- not_important Any time morning In the morning afternoon In the afternoon evening In the evening night In the night
Return flight time	prefered_back_departure_type	not_important Any time morning In the morning afternoon In the afternoon evening Evening night In the night
Search only among direct flights ("No transfer")	direct	true

Optional request parameters for one-way and round-trip route searches
Element	Variable	Allowable values
money_from	0 Integer number greater or equal to 0
Upper limitation to the default price	money_to	10000 Integer number greater than 0
Search for nearest dates	district_date	true
Range of neighboring dates +(-) [days]	date_range	- 1 An integer greater than [1...3]
Search for nearby airports	district_airport	true
Service class	class	econom Economy class flight business Business class flight first First class flight
Filter by airline	input_vendors	SU,PS IATA airline codes, separated by commas without spaces
Sorting	sort	price By price out_date On schedule By airline fltduration By flight length

Complex route

Attention! These variables only apply to the complex route (trip_type=CR).

Request parameters for complex route search
Element	Variable	Allowable values
Departure points	cr_iata[0] cr_iata[1] ... cr_iata[8]	MOW	IATA airport code
Arrival points	cr_back_iata[0] cr_back_iata[1] ... cr_back_iata[8]	LED	IATA airport code
Departure date	cr_date[0] cr_date[1] ... cr_date[8]	25.10.2013	Date in the format dd.m.yyyy
Departure time	cr_pref_departure[0] cr_pref_departure[1] . ... cr_pref_departure[8]	not_important Any time morning In the morning afternoon In the afternoon evening In the evening In the night
Service class	cr_class[0] cr_class[1] ... cr_class[8]	econom Economy class flight business Business class flight first First class flight
Nearest airports (±XX kilometers)	cr_district_airport[0] cr_district_airport[1] ... cr_district_airport[8]	true

[X] - the numbers of individual flights. The numbering starts with 0, which means the first flight.

The maximum number of segments for complex route is defined in Product control → Outdated Settings → Search Restrictions.

Passengers

Options for specifying passengers in the search request
Element	Variable	Allowable values
Adults from 12 years old	adults	Integer number greater or equal to 0
Children from 2 to 12 years old	children	Integer number greater or equal to 0
Infants under 2 years old	infants	Integer number greater or equal to 0
Infants with seat up to 2 years old	infants_seat	Integer number greater or equal to 0
Youth 12 to 24 years old	youths	Integer number greater or equal to 0
Seniors age 65 and over	seniors	Integer number greater or equal to 0

Fast Search for Frontend 2.0

Request parameters

When using Frontend 2.0, the following variables are available for the link: Parameters in the table are given in the order in which they should follow in the request.

Parameters for specifying passengers in a search request
Element	Entry format	Allowable values
Departure point	three-letter IATA code	MOW
		LED
Airport arrival point	The 3-letter IATA code of the airport	IEV
		MOW
rowspan="2"	Departure date in the format YYYYYMMDD	20160818
dX, where X is the offset of the departure date from the current date. A non-negative number.	d7
rowspan="3"| Passenger types and their quantity	The three-letter type code of the passenger (ADT,CLD,INF,INS,YTH,SRC) with the quantity	ADT2
ADT2INF2
ADT3INS1CLD2SRC1
Search only for direct flights	Command	-direct
Search only by nearest dates	Command	-vicinityDates
Class	Flight class name (Economy, Business, First)	-class=Economy
		-class=Business
		-class=First
Currency	Three-letter currency code (USD, EUR, RUB)	-ccCurrency=USD
Search process start. If the parameter is not specified, the parameters will be inserted in the search form, but the search process will not be started	-GO
Disabling redirect	?noredirect=1

Note. If it is necessary to pass parameters to the form without the dates of departure-arrival, leaving the date fields empty, you can substitute 8 zeros instead of specific dates, for example: /search/MOWMAD00000000ADT1-class=Economy. Then the user will choose the date himself, and the other passed parameters will be filled.

Examples

One way route

Direct one-way economy class itineraries from Moscow to Paris departing February 18, 2016 for three adults, two children and one infant with seat search by the nearest dates. Request fills in the search form http://SITENAME/search/MOWPAR20160218ADT3INS1CLD2-direct-vicinityDates-class=Economy Request starts the search process http://SITENAME/search/MOWPAR20160218ADT3INS1CLD2-direct-vicinityDates-class=Economy-GO

Round trip itinerary

Business class itinerary from Moscow to Berlin with departure in 10 days from the current date and back in 20 days from the current date for two adults. Request fills in the search form http://SITENAME/search/MOWBERd10BERMOWd20ADT2-class=Business . Questionnaire starts the search process http://SITENAME/search/MOWBER20160218d10BERMOW20160222d20ADT2-class=Business-GO

Complex route

Itinerary from Kiev to Peshevar with departure 10.07.2016, from Peshevar to Moscow with departure 18.07.2016, from Moscow to Paris, with departure 19.07.2016 for one adult. Request fills in the search form http://SITENAME/search/IEVPEW20150710PEWMOW20150718MOWPAR20150719ADT1 Request launches the search process http://SITENAME/search/IEVPEW20150710PEWMOW20150718MOWPAR20150719ADT1-GO

Interaction between Fast Search and the metrics module

In order to fix the source of the link which was used by the user you must pass additional parameter at the end of the request:

?utm_source=source_alias

where source_alias is the alias of the transition source of the metrics module.

Information about source of transition is displayed in logs and on the order page in service information.

Example of Fast Search for Frontend 1.0

Fast Search request for Frontend 1.0 including metrics module transition source

One way itinerary without transfer for one adult from Moscow to Paris with departure 25.10.2016 (taking into account metrics module transfer source). Request fills in the search form http://SITENAME/?trip_type=OW&out_iata=MOW&in_iata=PAR&departure_date=25.10.2016&direct=true&adults=2&param_by_get=on&utm_source=source_alias Request starts the search process http://SITENAME/?trip_type=OW&out_iata=MOW&in_iata=PAR&departure_date=25.10.2016&direct=true&adults=2&param_by_get=on&fast_search=on&utm_source=source_alias

Fast Search example for Frontend 2.0

Fast Search request for Frontend 2.0 considering source of metrics module

Direct one way economy class itineraries from Moscow to Paris with departure 18.02.2016 for three adults, two children and one infant with seat, searched by the nearest dates (taking into account metric module transition source). Request fills in the search form http://SITENAME/search/MOWPAR20160918ADT3INS1CLD2-vicinityDates-class=Economy?ccCurrency=USD&utm_source=source_alias Request starts the search process http://SITENAME/search/MOWPAR20171218ADT1-vicinityDates-class=Economy-GO?ccCurrency=USD&utm_source=source_alias

See also

• Search (Air tickets)
• Route type
• Metrics module
• Search form (Air tickets)