🧪 Experimental KB — Official knowledge hub: community.kaptio.com

← Back to KB
configuration

How to Connect a New or Refreshed Sandbox to KTAPI

When customers create new sandboxes or refresh existing ones, the KTAPI connection is lost and must be reconfigured. The sandbox needs to be connected to KTAPI with all external supplier gateways conf

sandbox KTAPI configuration rail-cache supplier-gateway setup

Problem

When customers create new sandboxes or refresh existing ones, the KTAPI connection is lost and must be reconfigured. The sandbox needs to be connected to KTAPI with all external supplier gateways configured and caches populated before it can be used for testing or development.

What We Found

New sandboxes require a complete KTAPI setup process that includes multiple configuration steps. Additionally, custom Flows may reference the deprecated Supplier__c field which must be updated to SupplierAccount__c to avoid errors during smoke testing.

Solution

  1. Customer creates/refreshes sandbox and provides: URL, Org ID, and Admin username
  2. Kaptio Support confirms email address and sends password reset link
  3. Set up KTAPI connection - authenticate and run initial full sync
  4. Configure External Supplier Gateways for Rail, Accommodation, Activities, and Transfers
  5. Enable Accommodation cache for package search
  6. Populate Rail Cache for package search (request platform team if needed via API ticket)
  7. Verify service searches work for all service types (Rail, Transfers, Activities, Accommodation)
  8. Check custom Flows for Supplier__c field references - update to SupplierAccount__c if found
  9. Update custom Apex classes if they reference deprecated Supplier__c field
  10. Complete smoke testing to validate end-to-end functionality
  11. Request customer testing validation before closing ticket

Notes

  • KTAPI full sync typically completes over a weekend for full copy sandboxes
  • HotelBeds availability varies by city - try larger cities like Amsterdam, Barcelona, or Cologne for testing
  • Rail cache population is handled by the platform team and may take additional time
  • The Supplier__c to SupplierAccount__c migration affects these Flow types: Itinerary confirmations, Itinerary Item confirmations, Payment Schedule updates
  • Test classes using deprecated fields may not block functionality but should be updated eventually

Warnings

⚠️ Custom Flows referencing Supplier__c will cause errors during smoke testing - must be updated before proceeding ⚠️ Both Flows AND Apex classes may need field reference updates

Source: KHELP-12243

Was this article helpful?