Certification process

Back to Fulfillment home.

Before production access is enabled, all implementations must pass the certification process. Certification verifies that your integration handles both the happy path and error scenarios correctly for each operation.

Prerequisites

  • A valid test environment credential (username and password) issued by your TravelCaster partner.
  • At least one test booking created through the TravelCaster flight booking flow (with issued tickets).
  • Confirmation from your TravelCaster partner that the test environment is ready.

Exchange certification

Execute the following scenarios in order. Each scenario must be completed successfully and the results submitted for review.

Scenario 1 — Full exchange flow

  1. Call InitializeExchange for a test booking and verify the response contains the expected itinerary, fare, and passengers.
  2. Call SearchExchangeAlternatives for at least one leg. Verify:
    • The response includes a RecommendationID.
    • At least one ExchangeOffer is returned with one or more Options per leg.
    • TotalDue, PenaltyAmount, and PaxFareDetails are populated.
  3. Select an offer and call FulfillExchange with the corresponding RecommendationID and ReplaceWithOptionRef values. Verify:
    • TransactionCode = "0".
    • The response contains updated itinerary and passenger data.

Scenario 2 — Recommendation expiry

  1. Call SearchExchangeAlternatives and capture the RecommendationID.
  2. Wait until the recommendation expires (or use an expired/invalid ID).
  3. Call FulfillExchange with the expired ID. Verify error code 3003 is returned.

Scenario 3 — Invalid offer selection

  1. Call SearchExchangeAlternatives and capture a RecommendationID.
  2. Call FulfillExchange with a ReplaceWithOptionRef that does not exist in any offer. Verify error code 3005 is returned.

Refund certification

Scenario 4 — Full refund flow

  1. Call PreviewRefund for a test booking with at least one refundable ticket. Verify:
    • RefundAvailable = true.
    • TicketDetails is populated with refundable amounts per ticket.
  2. Call FulfillRefund for the same booking. Verify:
    • TransactionCode = "0".
    • RefundSuccessful = true.
    • RefundedAmounts contains at least one entry with a non-zero amount.
    • TicketDetails contains at least one entry with Refunded = true.

Scenario 5 — Preview before refund

Verify that calling FulfillRefund without first calling PreviewRefund still succeeds and returns correct data. The preview step is recommended to the end user but is not enforced by the API.

Error handling certification

Scenario 6 — Authentication errors

  1. Call any operation with an empty or invalid token. Verify error code 1210 is returned.
  2. Call any operation with an expired token. Verify error code 1210 is returned.

Scenario 7 — Permission errors

Call InitializeExchange or PreviewRefund with a booking number that belongs to a different agency. Verify error code 3000 is returned.

Submission

After completing all scenarios, provide your TravelCaster partner with:

  • Request and response logs for each scenario (JSON).
  • Confirmation of the test booking numbers used.
  • Any integration notes or questions.

Your partner will review the logs and confirm certification or request adjustments.

Back to Fulfillment home.

See change history for this file
Loading...