Certification Process

Back to Flights home.

After you have developed your connector for the TravelCaster API, you will have to go through a certification process to verify that your requests interact correctly with our system. This process includes performing several bookings under different scenarios, requesting ticketing or cancellation, and retrieving notifications.

The certification process takes place within a specific time slot to allow for the verification of logs and booking interactions. When you request certification, you will be assigned a slot within the next 5 days to perform the required operations. After completing them, you must provide the following information for verification:

  • Certification Questionnaire
  • Certification Scenarios:
    • Provide all scenarios based on your certification questionnaire.
    • Provide all trace logs (request and response) in JSON format for each scenario.
  • Capacity Questionnaire

During the certification process, you will be in direct contact with the Starligs technical team to analyze your integration. Once the certification is completed, all subsequent questions and inquiries must be managed through Zendesk.

If the certification is successful, you will receive the production environment endpoint and credentials. If there are any objections or errors, you will be notified to fix them and rerun the process.

Certification Questionnaire

  • Question A: Which ticketing service will you implement?
  • Question B: Will you implement Credit Card payment?
  • Question C: Will you implement the Void ticket functionality?
  • Question D: Will you sell infant tickets?
  • Question E: Will you implement the Ancillary-Bag functionality?
  • Question F: Will you implement the Alternative Fares functionality?
  • Question G: Will you implement the Ancillary-Seat functionality?

Certification Scenarios

  • Scenario 1:

    • Search and book a one-way flight for 2 adults.
    • Call RetrieveBooking.
    • Request cancellation.

  • Scenario 2:

    • Search and book a round-trip flight for 1 adult.
    • Call RetrieveBooking.
    • If Question B = true: Call UpdateBookingPayments to update the form of payment to CreditCard. You can use the test card VI 4444333322221111.
    • If Question B = true: Call RetrieveBooking.
    • Request ticketing.
    • If Question C = true: Request void.

  • Scenario 3:

    • Search and book a round-trip flight for 2 adults on a specific carrier (e.g., LA), setting NATL and FOID if required.
    • Call RetrieveBooking.

  • Scenario 4: (Run this scenario only if Question D = true)

    • Search and book a round-trip flight for 2 adults, 1 child, and 1 infant.
    • Optional: If your logic updates the form of payment after booking, request the FOP update.
    • Call RetrieveBooking.
    • Request ticketing.

  • Scenario 5: (Run this scenario only if Question E = true)

    • Search and book a round-trip flight for 2 adults, requesting ancillaries for both.
    • Call RetrieveBooking.
    • If Question B = true: Call UpdateBookingPayments to update the form of payment to CreditCard (VI 4444333322221111).
    • If Question B = true: Call RetrieveBooking.
    • Request ticketing.

  • Scenario 6: (Run this scenario only if Question F = true)

    • Search and book a round-trip flight for 1 adult requesting alternative fares.
    • Call RetrieveBooking.

  • Scenario 7: (Run this scenario only if Question G = true - PreBook Logic)

    • Search a round-trip flight for 2 adults for an NDC-LA carrier.
    • Quote the selected option using ConfirmFlightAvailability or GetFareOptions.
    • Request GetSeatMap and book one seat for the inbound and two seats for the outbound flights.
    • Call RetrieveBooking.
    • Request ticketing.

  • Scenario 8: (Run this scenario only if Question G = true - PostBook Logic)

    • Search and book a round-trip flight for 2 adults for a carrier that implements PostBook logic.
    • Call RetrieveBooking.
    • Request GetSeatMapForBooking and book one seat for the inbound and two seats for the outbound flights.
    • Call RetrieveBooking.
    • Request ticketing.

Capacity Questionnaire

  • Capacity A: Estimated flight scans (GetFlightAvailability) per day:
  • Capacity B: Estimated requests (all transactions) per day:
  • Capacity C: Estimated maximum simultaneous transactions (QPS - queries per second):
  • Capacity D: Estimated peak hours ranges:
  • Capacity E: Estimated Bookings per day:

Back to Flights home.

See change history for this file
Loading...