Availability

Avail overview


Our availability method have many search options, and you have the possibility of customizing the results base on your business objetives.

 

1 - Search types

There are 3 diferents search: One Way, Round Trip and Open Jaw, add in "journeys" as origin-destination you need.

 

One Way : describes journeys which go to just one place, without return

example

MAD NYC ( Madrid - New york )

 

 

Round tryp : round-trip are journeys from and back to the same location of origin

MAD NYC

NYC MAD

Depending on the provider, buying two one way tickets may or may not be more expensive than buying a round trip ticket.

 

 

Open Jaw: An open jaw itinerary is one which the destination may be one city; but the city from which you are returning is different. 

The maximun number of origin and destination flights are 6

Example

MAD MIA = Madrid Miami

NYC LAX = Miami Los Angeles

regresando desde LAS = Las Vegas hacia Madrid

 

 

2 - Mandatory parameters

 

Building a basic query: The following mandatory parameters need to be taken in account for a basic search

 

Pax_distribution = You only need to add the age of each passenger

Passenger

The only value to change on Avail RQ is the age of each passenger and it will become the type of passenger that corresponds according to age

Example of ADT (adult) CHD( Child ) INF (infant )

 

], "paxes_distribution": { "passengers_ages": [ 30, 7, 1 ]

 

 

Avail for Adult Chid and Infant example https://lleego.atlassian.net/wiki/spaces/APIDOC/pages/412615193

 

Journeys = is the node that contains the information of the trip to be requested on Avail method

Origin = IATA Code

Destination = IATA Code

 

Example Roud trip

 

}, "journeys": [ { "origin": "MAD", "destination": "NYC", "date": "2019-11-17" }, { "origin": "NYC", "destination": "MAD", "date": "2019-11-30" }

 

 

 

Date = Lleego use the following format to add the dates on each travel segment

 

Example dates ( Round trip)

"date": "2019-11-17" departure

"date": "2019-11-30" return

"journeys": [ { "origin": "MAD", "destination": "NYC", "date": "2019-11-17" }, { "origin": "NYC", "destination": "MAD", "date": "2019-11-30" } ]

 

 

Basic AVAIL Search example One Way

 

 

 

3 - Optional and customized Parameters

 

You can customize your Avail query base on your business needs adding rules and optional parameters like , Flexibility, scales, hours, fare types , non stop flights , cabin type , rules etc

check the following URL to know about optional parameters not mandatory

 

 

Example of customize Avail with rules

 

 

Fare Types

You can select the type of fares you want to get on Avail response , if you do not select the type fare we will return all fare types ( Public and private)

 

Public= public fares this type of fares can be distribuited in all providers

Private= Special agreeement between airline and travel agency , this type of fares can be distribuited in some office ids , RP and tarvel agencies .

Corporate= Is a type of private fare between airline and agency who needs special identification *corporate code *to get on the avail results and quote

 

 

4 -Special cases

There are some special cases like Residents, Large families and UNMR Unaccompanied Minor . Pls add the param and follow the booking workflow for this cases.

 

Large family discount

Special discount between 5 and 10 % for family with three or more children

 

Unaccompanied Minor

Special service for children traveling alone

You must to add the age of child traveling alone on query

 

Special scenarios samples

 

 

Resident Discount

 

 

The Balearic or Canary discount is a special discount 75% that applies to Spanish or European Community who legally reside in Canary or balearic Islands and Ceuta and Melilla Spain.

The DNI and place of resident should be add on Book method

 

Avail query is equal to non residents because Resident discount need to be added on Pricing Method and additional information like dni and resident code need to be added on book

Check the resident link for complete flow and info

 

 

 

 

Avail Response


It is very important that you understand the response, and remember that you receive what you send in rules.

Partial solutions : When you request a *partial solution * Aval response get information of one way options and you could build your trip using oneway fares

Depending on the provider, buying two one way tickets may or may not be more expensive than buying a round trip ticket but you need to be careful because when you sell a Roud trip ticket built with two one-ways if one provider makes any changes on itinerary the other provider may refuse to realocate the passenger it is like selling two tickets separately.

 

Solutions

A travel solution ID contains all the information related itinerary it may be built by

Roud trip or one way travel, it contains the journey reference with all the segment reference into

 

Parametres and mapping explanation

 

  • Segments (Direct flights)

  • Journeys (1 o more segments)

  • Origindestinations (journeys grouped)

  • Fares (Information about fare )

  • Partial solutions (Information of OW journeys options) You obtain as partials solutions as your request (OW = 1, RT = 2 OJ = 2-6)

  • Solutions (RT and combined flights solutions)

  • Data (Statics data like company name, airports, etc...)

 

Maping the information

Each solution id contains the node Asociation with journey references into , with all the details of itinerary : Fare Base , fligh number , provider , total fare, total taxes , fare type , fare family , passenger type , baggage allowance, cabin type , service fee etc

 

Mapping Example

Solution ID into this node journeys asociation with journey references

"solutions": [{
"id": "fN60f7fe88ebde10000",

 

 

Example Journey node with all flight information into

 

 

 

 

Avail response sample