Skip to content

Launch Protocol

Goal: The launch protocol ensures a smooth launch and makes sure both you and Gordian are on the same page once live traffic begins to roll in.

Pre-launch testing should be conducted with engineers from Gordian and the partner together on a call before partner is issued a production key to go live. Partners should design their systems in such a way that E2E testing can be performed in sandbox or cert environments. During testing, partners should perform the bookings themselves and should not use live customer bookings for testing. The partner should ensure that following the testing session, all test bookings (and ancillaries) are successfully voided with the airline.

The partner will complete several end-to-end bookings and Gordian engineers will monitor the process and request coming from the partner.

Testing Protocol

  1. Trip Creation
    • We will verify all parameters provided in the partner’s Trip Creation request.
      • Markups (if applicable)
      • Fare class
      • Fare basis
      • Fare family
  2. Search Creation
    • We will verify the search parameters, and ensure that partners have access to all the necessary content.
  3. Add ancillaries to basket
    • Verify that the ancillaries Gordian received in the request correspond correctly to the ones partner intended to add.
      • Verify price, product name, item validity
  4. Fulfillment Request
    • Verify that the fulfillment request contains information needed for booking, such as access details for the booking.
  5. Verify Fulfillment Callbacks
    • Upon booking completion, Gordian verifies in our database that a callback was sent.
    • Partner confirms that callback was received with correct format and that their systems have updated.
  6. Trip Access Token Use

    • Verify that all API request from client side to Gordian's endpoint are made using the trip access token.
  7. Portal (if applicable)

    • The partner logs into the portal with their own credentials and verifies the test booking is present and correct.
  8. Refund Check, Portal and Callbacks (if applicable)
    • The partner initiates a Refund Check through the portal.
    • Gordian verifies that we have received refund check and either completes or rejects the Refund Check
    • Gordian verifies in our database that a callback for the Refund Check was sent
    • Partner confirms that a callback was received for the refund check, if applicable, and that their systems have updated.
    • Partner verifies the correct Refund Check status in the portal
  9. REPEAT the above steps for the following types of bookings, each performed with a different carrier if possible:
    • 1 pax, 1 ancillary, Gordian marks as Fulfilled
    • 1 pax, 1 ancillary, Gordian marks as Failed
    • 2 pax, 1 ancillary each, Gordian marks both Fulfilled
    • 2 pax, 1 ancillary each, Gordian marks both Failed
    • 2 pax, 1 ancillary each, Gordian marks one Fulfilled, One Failed