Originally Posted by
ldpeters
Fine. Then how do you use EF to check bucket availability for complex routings/iteneraries containing more than four specified segments (as EF only allows departing, destination, and two connecting airports).
Furthermore, if bucket availability is for the whole routing/itenerary, how do you check availability segment-by-segment to build a complex itenerary with multiple stops over multiple days?
I usually use ITA software for more complicated itens like this by using multiple segments with the /f bc= switch in the search. For example, if you're looking for NYC-HNL in V followed by HNL-NRT in H then you'd do
Segment 1
From: NYC:: AA DFW AA /F bc=v
TO: HNL
Segment 2
From: HNL:: AA+ /F bc=h
If you need to search in more than one inventory for the segments, use the vert. bar to separate the bc= expressions. For example to do v and w inventory search for seg. 1 you can do
NYC:: AA DFW AA /F bc=v|bc=w
As for your follow-up question, not only will bucket inventory differ for different routings on the same metal, but the prices will be different, too.
For example, your iten from NYC-HNL via DFW may cost you around $600 in V, but not show much availability, while the NYC-DFW segments will show lots of V availability. If you were to price that V ticket NYC-DFW (to trick the system into multiple R/Ts), you'll find that the price of NYC-DFW alone in V is over $1000 (all hypotheticals, but not far from the truth).