Durations and totals

[tommiehansen]

Include duration for each leg (flight) and total durations (itinererary level) for all GET responses or alternative include the timezone (UTC +/- DST) for each time format so one can calculate the durations more easily.

[tadhgpearson]

Thanks for the feedback Tommie. You're totally right, the correct way to do this would be to include the timezone offset in the date-time response, as we do in the Travel Record API. This would allow you to easily calculate the duration and enable a bunch of cool new ways to display flights. Unfortunately it's too late to change the date format in the current version of the flight APIs, as this wouldn't be backwards compatible. However, we will include it in the next version!

[tommiehansen]

Ok, thanks for the quick reply.

[hari-rangarajan]

@tadhgpearson Any developments on this in recent releases? It looks like the flight search should return 'durations' as per the spec but don't see this field being populated from the server.

    'flights': Array<FlightSearchSegment>;
    /**
    * The duration of this bound, including layover time, expressed in the format hh:mm
    */
    'duration': string;

[tadhgpearson]

@xmulot - any comment on this?