-
Notifications
You must be signed in to change notification settings - Fork 1
Avia searches
this documents contains instructions on how to construct link to search results on eviterra.com for flight origin and destination and dates of your choice.
please note, that we do not provide (yet) IATA <=> city/airport name dictionaries, you have to have dictionaries on your side to use that API.
<a href='http://api.eviterra.com/avia/v1/searches?from=MOW&to=LED&date1=2012-09-25&partner='>Moscow-St.Petersburg flights</a>
http://api.eviterra.com/avia/v1/searches?arg1=value&arg2=value...
from
or from1
IATA code of departure city/airport
to
or to1
IATA code of arrival city/airport
date1
YYYY-MM-DD date of departure
date2
YYYY-MM-DD date of departure for a roundtrip journey. Should be omitted for oneway search.
from2
, to2
- IATA codes for second segment if date2
specified. If ommitted then it's a roundtrip search (from2
= to1
and to2
= from1
)
from3
, to3
, date3
... from6
, to6
, date6
- Complex route. When fromN
isn't specified, it's assumed to be equal with toN-1
.
adults
"1" if omitted!
children
"0" by default
infants
"0" by default
cabin
preferred booking class, could (and probably should) be omitted. "Y" for economy, "C" for business, "F" for first/premium. Empty by default (no preference)
partner
your company identificator
marker
your internal (string) tracking code for a particular redirect, if you need one.
on non valid data we'll try to redirect user to our homepage, still marking visitor with your "partner" token
redirect (HTTP status code "302 Found") to corresponding search results on our site ("Location:" HTTP Header)