Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

connecting recommendation with flighs & baggage info #235

Closed
rifkydj opened this issue Sep 27, 2018 · 6 comments
Closed

connecting recommendation with flighs & baggage info #235

rifkydj opened this issue Sep 27, 2018 · 6 comments

Comments

@rifkydj
Copy link

rifkydj commented Sep 27, 2018

Hi guys,

Im using Fare_MasterPricerTravelboardSearch API,

I want to know how to connect recommendations with flights & baggage info .Im using laravel . if someone provide me explanation with code it will be a great help for me.

Thanks

@therealartz
Copy link
Collaborator

therealartz commented Sep 27, 2018

Here are response from Amadeus support (which You should be contact when facing difficulties in work with Amadeus).
This answer helped me understand how to work with MPTB response.

A Recommendation is a combination of groupOfFlights. If we consider a Round Trip itinerary as an example (Master Pricer Response attached), we’ll have:

  • segRef: 1 for the outbound and 2 for the Inbound
  • Each segRef has groupOfFlights and in flightDetails you can find the details in terms of Carrier(s), Time(s) of Departure, location(s), etc. Here’s an example of an outbound connecting flight (number 15 in the Outbound groupOfFlights):

attachment 1

  • As mentioned before, a Recommendation is a combination of groupOfFlights. Per definition, one recommendation is composed by a Fare + flights. However, two recommendations may have the same Fare but different combination of flights.

  • As an example, the Recommendation number 7 (with a total Fare of USD 324.00) has 4 possible combination of flights. The first one makes reference to groupOfFlights 15 for the Outbound and 7 for the Inbound (refQualifier S = 15 and S = 7 respectively).

attachment 2

@rifkydj
Copy link
Author

rifkydj commented Sep 28, 2018

Hi i dont have access to open attachments. please grant permissions.
Thanks

@rifkydj rifkydj closed this as completed Sep 28, 2018
@rifkydj rifkydj reopened this Sep 28, 2018
@therealartz
Copy link
Collaborator

@rifkydj links updated. Check them now.

@rifkydj
Copy link
Author

rifkydj commented Sep 29, 2018

@therealartz Hi i checked . what u mean is recommondation array's referencing details->refNumber indicates flightindex->groupOfFlights->proflightGRdetails->flightproposal->ref ?????

i have two questions.

1).Recommendation array refNumber is repeating 2 times.

for example
S 1
S 1
B 1

S 1 is repeating. What is the meaning of this?

2). when connecting recommendations with flights some references are not matching.

for example if 57 th recommendation has refNumber as 24 , in flightinde-> flightproposal->ref doesn't have ref as 24 .
How can i handle this?????

@therealartz
Copy link
Collaborator

  1. It means that you've search the recommendations for two segments and the given recommendation consists of two segments (itineraries).
    S 1 - flightIndex[0]->groupOfFlights[0] // First flight from flightIndex for first segment.
    S 1 - flightIndex[1]->groupOfFlights[0] // First flight from flightIndex for second segment.
    B 1 - "B" stands for "Baggage coverage reference". It referencing to reply->serviceFeesGrp->freeBagAllowanceGrp where you should find baggage allowance under this ref number.
    Codes description can be find at reply structure of message at extranet.

  2. I am not an Amadeus expert, but perhaps you are looking for refNumber in the wrong flightIndex (which is related this to your first question).

If you really wish to develop with using Amadeus WS you should learn to navigate in messages documentation at extranet.

@rifkydj
Copy link
Author

rifkydj commented Sep 29, 2018

@therealartz thanks broo. ill try .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants