API Changes

Follow

Comments

1 comment

  • Avatar
    fredy.bryan

    Hi,

    As they were informed weeks ago, the airline seeks to migrate those that are branded BrandedFares, so and looking to have progressive changes for our Direct Connect– NDC channel, we require your collaboration to be able to adjust and validate the results that are made regarding the CFF change. We enclose the example of the complete XML for review.

    Old: CFFARDW

    New: CFFNDCECO & CFFNDCBUS

    Airshopping extract:

    <ns:Preference>

                    <ns:FarePreferences PreferencesContext="CFFNDCECO"/>

    </ns:Preference>

    As Amadeus informs us, there should be no impact on having the previous ones, but we seek to validate with you if by adjusting your side we can continue to receive information without inconvenience. Please check with flights from DIC19.

    Given the migration strategy, which has the activation of Branded Fares for Origin / Destination ECU since 24SEP19, and then Colombia since 01NO19, the idea is to address the new CFF to ECU and keep targeting the other markets the old CFF, while we continue with the migration plan in the other markets.

    UIO

    GYE

    GYE

    UIO

    UIO

    GPS

    GPS

    UIO

    SCY

    GYE

    GPS

    GYE

    UIO

    SCY

    SCY

    UIO

    UIO

    OCC

    OCC

    UIO

    UIO

    MEC

    MEC

    UIO

    GYE

    MEC

    GYE

    OCC

    GYE

    SCY

    GYE

    GPS

    MEC

    GPS

    MEC

    SCY

    OCC

    GPS

    OCC

    SCY

    We share the OD's of Ecuador, with their possible combinations so that the new CFFs are consumed only since 24SEP19, while the migration to the other countries is made:

    I remain attentive to your comments or any clarification.

    Best Regards,

    Fredy Bryan

    0
    Comment actions Permalink

Please sign in to leave a comment.