Cyberesa Developers V2027.0.x
Flight API · Search & pricing

FlightStartSearch

This function is designed to search flights availability and fares for GDS and LCC content. It returns available flights for GDS and then launch routers searching LCC suppliers in relation to the search request.

It facilitates a wide range of options, ensuring that customers can narrow down or broaden the flights search, in order to precisely match their request.

Request

XML
<FlightStartSearchRQ>
  <Credentials>
    <Login>?</Login>
    <Password>?</Password>
  </Credentials>
  <User>?</User>
  <OfficeIds>
    <OfficeId Curr="?">?</OfficeId>
    <OfficeId>?</OfficeId>
  </OfficeIds>
  <Curr>?</Curr>
  <Ilng>?</Ilng>
  <Flight>
    <Content>?</Content>
    <Passenger>
      <Adult>?</Adult>
      <Child>?</Child>
      <Infant>?</Infant>
    </Passenger>
    <FareOptions>
      <Type>?</Type>
    </FareOptions>
    <FlightOptions>
      <Class>?</Class>
      <Company>?</Company>
      <FlightType>?</FlightType>
      <AirportOnly>?</AirportOnly>
      <Luggage>?</Luggage>
    </FlightOptions>
    <Itineraries>
      <Itinerary>
        <Ref>?</Ref>
        <Class>?</Class>
        <Departure>
          <Code>?</Code>
          <Type>?</Type>
        </Departure>
        <Arrival>
          <Code>?</Code>
          <Type>?</Type>
        </Arrival>
        <TimeDetails>
          <Date>?</Date>
          <RangeOfDate>
            <Qualifier>?</Qualifier>
            <Interval>?</Interval>
          </RangeOfDate>
          <Time></Time>
          <RangeOfTime>
            <Interval>?</Interval>
          </RangeOfTime>
        </TimeDetails>
      </Itinerary>
    </Itineraries>
  </Flight>
</FlightStartSearchRQ>
RootSub rootTagDescriptionValues & Format
CredentialsMandatory
LoginMandatory
PasswordMandatory
UserMandatory
OfficeIdsOptionalIf you don’t specify any officeId, we use the first one in DBOnly for GDS
OfficeIdOptionalalphanumeric characterOnly for GDS
OfficeId:CurrOptional3 alphanumeric characterOnly for GDS to specify the currency per office id
CurrOptional3 alphanumeric characterGDS : We use this node
for officeid without attribute curr.
IlngMandatoryNumeric valueDefault value 2 (English)
FlightMandatory
ContentMandatoryType of requested flightsall,
LCC : low cost flights,
GDS : regular flights,
Train: low cost trains
PassengerMandatoryThis parameter is designed to specify the number of seats required for the travelling passengers of flightsMaximum 9 passengers
Passenger:AdultMandatoryNumeric valueAt least one adult must be specified
Passenger:ChildMandatoryNumeric valueIt can be 0 or plus
Passenger:InfantMandatoryNumeric valueIt can be 0 or plus
FareOptions:TypeOptional(GDS only)The user has the ability to between two types of fare :
*No Restriction, return all available flights without restriction
*Refundable, return only flights that may be refundable
NR : No Restriction
RF : Refundable fares
Default value NR
FlightOptions: ClassOptional(GDS only)The user has the ability to specify a desired cabin class of requested flightsM : Standard economic
W : Premium economic
Y : Economic
C : Business
F : First
FlightOptions: CompanyOptional(GDS only)The user has the ability to specify which operator he wants of requested flights2 alphanumeric character
FlightOptions: FlightTypeOptionalThe User has the ability to request Non-Stop or Direct flights; or also a combination of these categoriesN: Direct (No-Stop)
D: Direct (with technical stopover)
X: Direct (No-Stop) & Direct (with technical stopover)
E: Exclude mixed company
FlightOptions: AirportOnlyOptionalThe User has the ability to propose nearby airports or only exact airportsTrue or False by default False
FlightOptions: RejectMixedOptionalThe User has the ability to request only flights companies.True or False by default False
FlightOptions: LuggageOptionalThe User has the ability to request flights with bagsTrue : filter flights with bags
Other value or no node : return all flights
Itineraries:
Itinerary:
MandatoryAt least one itinerary
RefMandatoryRank of itinerary for requested flights, Numeric valueIncremental value, initial value is 1
ClassOptional(GDS only)The user has the ability to specify a desired cabin class of requested itineraryM : Standard economic
W : Premium economy
Y : Economic
C : Business
F : First
DepartureMandatoryThe user must specify a departure location, each location is composed of
Departure:CodeMandatoryInternational code of airport or city3 alphanumeric character
Departure:TypeType of locationAirport
City
ArrivalOptionalThe user must specify an arrival location, each location is composed of
Arrival:CodeMandatoryInternational code of airports or cities3 alphanumeric character
Arrival:TypeOptionalType of locationAirport
City
TimeDetails:DateMandatoryThe earliest date that a recommended flight may "depart from"dd/MM/yyyy
TimeDetails:
RangeOfDate
Optional(GDS only)The User has the ability to request that the requested flights include the day before or the day after the date specified for an itinerary
TimeDetails:
RangeOfDate:
Qualifier
Optional(GDS only)P : Plus
M : Minus,
C: Plus & Minus
TimeDetails:
RangeOfDate:
Interval
Optional(GDS only)It is currently not possible to request more than 1 day forward and/or1 day backward for the searchable date range[1..2]
TimeDetails:
Time
Optional(GDS only)The earliest time that a recommended flight may "depart from"HH:MM
TimeDetails:
RangeOfTime:
Inetrval
Optional(GDS only)The User has the ability to specify an applicable time window range, in terms of hours, to a specified time by departure option.
Thus, allowing the requested flights include any flight recommendations that depart within the specified number of hours on either side of the specified time by departure
[1..12]

Response

XML
<FlightStartSearchRS>
  <lcc>
    <CarrierCode>?</CarrierCode>
    <Suppliers>
      <Supplier>?</Supplier>
      <Supplier>?</Supplier>
    </Suppliers>
  </lcc>
  <Flights>
    <Flight>
      <Content>?</Content>
      <Currency>?</Currency>
      <Amount>?</Amount>
      <Duration>?</Duration>
      <Stops>?</Stops>
      <SFM>?</SFM>
      <OfficeId>?</OfficeId>
      <Itineraries>
        <Itinerary>
          <Ref>?</Ref>
          <Duration>?</Duration>
          <Stops>?</Stops>
   <AvailableSeats>?</AvailableSeats>
   <Segments>
            <Segment>
              <FlightId>?</FlightId>
              <Operator>?</Operator>
              <Equipment>?</Equipment>
              <Depart>?</Depart>
              <DepartDate>?</DepartDate>
              <DepartTime>?</DepartTime>
              <DepartTerminal>?</DepartTerminal>
              <Arrive>?</Arrive>
              <ArriveDate>?</ArriveDate>
              <ArriveTime>?</ArriveTime>
              <ArriveTerminal>?</ArriveTerminal>
              <Class>?</Class>
              <BookingClass>?</BookingClass>
              <AvailableSeats>?</AvailableSeats>
            </Segment>
          </Segments>
 </Itinerary>
      </Itineraries>
    </Flight>
  </Flights>
</FlightStartSearchRS>
RootSub rootTagDescription
lccOptionalAvailable only if the value of parameter "Content" in request is "all, lcc or train"
CarrierCodeOptionalCarrier code to be used to get lcc flights
Suppliers : SupplierOptionalList of Supplier which can assume lcc flights
Flights:Flight
ContentMandatoryType of flight : always GDS
C
urrency
MandatoryCurrency’s code used to calculate Flight Amount
3 alphanumeric character
AmountMandatoryAmount of flight
DurationMandatoryDuration of flight
StopsMandatoryTotal stop of flight
OfficeIdMandatoryOfficeId to be used for API FlightDetailRQ, Only for GDS
SFMOptionalContains Amadeus service fees, to be used for API FlightDetailRQ, Only for GDS
Itineraries: ItineraryMandatoryResponse for each requested itinerary
RefMandatoryRank of itinerary for the flight
DurationOptionalDuration of itinerary : 99h99m
StopsMandatoryCount of stops for the itinerary
AvailableSeatsMandatoryThis node serves to check the number of available seats by itinerary
Segments:
Segment
MandatoryEach itinerary can be composed by one or more segments
FlightIdMandatoryNumber of flight for the segment
OperatorMandatoryUsed operator for the segment
EquipmentOptionalUsed equipment for the segment
DepartMandatoryDeparture location for the segment
DepartDateMandatoryDepart date for the segment : dd/MM/yyyy
DepartTimeMandatoryDepart time for the segment : HH:MM
DepartTerminalOptionalUsed terminal for the segment
ArriveMandatoryArrive location for the segment
ArriveDateMandatoryArrival date for the segment : dd/MM/yyyy
ArriveTimeMandatoryArrival time for the segment : dd/MM/yyyy
ArriveTerminalOptionalUsed terminal for the segment
ClassOptionalType of class for the segment
BookingClassOptionalType of booking class for the segment
AvailableSeatsOptionalThis node serves to check the number of available seats by segment

Example

Request

XML
<FlightStartSearchRQ>
  <Credentials>
    <Login>Cu2gOrbzhN0=</Login>
    <Password>mtPXhFzrzuM=</Password>
  </Credentials>
  <User>707</User>
  <OfficeIds>
    <OfficeId>OOOO01</OfficeId>
    <OfficeId>OOOO02</OfficeId>
  </OfficeIds>
  <Curr>MAD</Curr>
  <Ilng>1</Ilng>
  <Flight>
    <Content>all</Content>
    <Passenger>
      <Adult>1</Adult>
      <Child>0</Child>
      <Infant>0</Infant>
    </Passenger>
    <FareOptions>
      <Type>NR</Type>
    </FareOptions>
    <FlightOptions>
      <Class>M</Class>
      <Company>AF</Company>
      <FlightType>N</FlightType>
      <AirportOnly>True</AirportOnly>
    </FlightOptions>
    <Itineraries>
      <Itinerary>
        <Ref>1</Ref>
        <Departure>
          <Code>PAR</Code>
          <Type>City</Type>
        </Departure>
        <Arrival>
          <Code>TUN</Code>
          <Type>City</Type>
        </Arrival>
        <TimeDetails>
          <Date>01/10/2012</Date>
          <RangeOfDate>
            <Qualifier>P</Qualifier>
            <Interval>1</Interval>
          </RangeOfDate>
        </TimeDetails>
      </Itinerary>
    </Itineraries>
  </Flight>
</FlightStartSearchRQ>

Response

XML
<FlightStartSearchRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <lcc>
    <CarrierCode>V14EVYBWRB1EY35S</CarrierCode>
    <Suppliers>
      <Supplier>Air Mediterranee</Supplier>
      <Supplier>Transavia</Supplier>
    </Suppliers>
  </lcc>
  <Flights>
    <Flight>
      <Content>gds</Content>
      <Currency>MAD</Currency>
      <Amount>11777</Amount>
      <Duration>02h30m</Duration>
      <Stops>0</Stops>
      <OfficeId>OOOO01</OfficeId>
      <SFM>0</SFM>
      <Itineraries>
        <Itinerary>
          <Ref>1</Ref>
          <Duration>02h30m</Duration>
          <Stops>0</Stops>
          <AvailableSeats>7</AvailableSeats>
          <Segments>
            <Segment>
             <key>?</Key>
              <FlightId>2184</FlightId>
              <Operator>AF</Operator>
              <Equipment>319</Equipment>
              <Depart>CDG</Depart>
              <DepartDate>01/10/2012</DepartDate>
              <DepartTime>07:35</DepartTime>
              <DepartTerminal>2F</DepartTerminal>
              <Arrive>TUN</Arrive>
              <ArriveDate>01/10/2012</ArriveDate>
              <ArriveTime>09:05</ArriveTime>
              <ArriveTerminal>M</ArriveTerminal>
              <Class>M</Class>
              <BookingClass>B</BookingClass>
              <AvailableSeats>7</AvailableSeats>
            </Segment>
          </Segments>
        </Itinerary>
      </Itineraries>
    </Flight>
  </Flights>
</FlightStartSearchRS>
CYBERESA SARL au capital de 560 000 TND (R.C : B2437152011 – M.F : 1189611/V) Siège social : Immeuble 3S, Lotissement Ennassim, 1073 Montplaisir - Tunis - TUNISIE · Tél : +216 71 947 401 - Fax : +216 70 201 010 - Site web : www.cyberesa.net - Email : info@cyberesa.net 30/10/2023 –
© Cyberesa · Flight API V2027.0.x · updated 27/08/2026