🔗 Prerequisites
Features
What you get with this outcome
Turn Your Website Into a Booking Engine
Your website is your 24/7 sales channel. Kaptio's eCommerce APIs enable real-time package search, availability checks, and booking submission directly from your website. The Belmond Booking Engine integration demonstrates the full flow: product catalog via KT Core API, booking creation via KT eCommerce API, and payment processing through KT Pay. Whether you build a custom IBE or integrate with existing web infrastructure, Kaptio provides the API foundation.
Visual coming soon
api-integration-diagram
KT Core API
Access your product catalog programmatically. Search packages, retrieve pricing, check availability, and pull content. Powers the search and browse experience on your website with real-time data from Kaptio.
- ✓Package search and filtering
- ✓Real-time availability
- ✓Dynamic pricing retrieval
- ✓Content and media access
Visual coming soon
KT eCommerce API
KT eCommerce API
Create and manage bookings through API calls. Submit passenger details, select services, calculate prices, and confirm reservations. Full booking lifecycle management without Salesforce UI access.
- ✓Booking creation and submission
- ✓Passenger data handling
- ✓Service selection and pricing
- ✓Booking confirmation workflow
Visual coming soon
Payment Integration
Payment Integration
Process payments through KT Pay or your existing gateway. Secure tokenization, PCI compliance, and automatic transaction recording. Customers complete payment without leaving your branded experience.
- ✓Secure payment processing
- ✓Multiple gateway support
- ✓Tokenization for recurring
- ✓Transaction reconciliation
Visual coming soon
Data Synchronization
Data Synchronization
Keep website and Kaptio in sync. Webhook notifications push updates, scheduled syncs refresh catalog data, and real-time availability prevents overselling. Heroku Connect enables direct database synchronization.
- ✓Real-time availability sync
- ✓Webhook event notifications
- ✓Scheduled catalog refresh
- ✓Heroku Connect integration
User Journey
Step-by-step flow from start to finish
🗺️User Journey Flow
Follow the steps from start to finish
Implementation Plan
How to implement this outcome
📅 Project Overview
API Setup
Week 1-2- • Configure API authentication
- • Set up sandbox environment
Integration Development
Week 3-6- • Implement search integration
- • Build booking submission flow
Resources
Configs, tools, and documentation to help you
API Architecture
Kaptio provides a comprehensive API ecosystem for website integration:
API Endpoints
| API | Purpose | Key Endpoints |
|---|---|---|
| KT Core API | Product data | /packages, /services, /availability |
| KT eCommerce API | Booking flow | /bookings, /passengers, /payments |
| KT Pay API | Payments | /transactions, /refunds |
Authentication
APIs use OAuth 2.0 authentication with Connected App credentials.
Booking Flow
End-to-End Sequence
- Customer searches on website
- Website calls KT Core API for packages
- Customer selects package/dates
- Website calls availability/pricing
- Customer enters details
- Website submits to KT eCommerce
- Payment processed via KT Pay
- Booking created in Salesforce
- Confirmation email sent## Data Synchronization### Options| Method | Use Case | Frequency | |--------|----------|-----------| | API Calls | Real-time queries | On-demand | | Webhooks | Event notifications | Real-time | | Heroku Connect | Database sync | Near real-time | | Scheduled Jobs | Catalog refresh | Daily/hourly |## Belmond ExampleThe Belmond Booking Engine (BBE) integration demonstrates:
- Product catalog via KT Core API
- Booking submission via KT eCommerce
- OSC profile synchronization
- GDPR-compliant data handling
Common Pitfalls
Avoid these implementation mistakes
Don't cache availability too long—stale data causes overselling
Implement proper error handling—API failures need graceful fallbacks
Test payment flows in sandbox—production payment errors lose customers
Plan for high traffic—peak booking periods need API rate limit management
Secure API credentials—exposed keys create security vulnerabilities
Handle PII carefully—GDPR compliance applies to web-collected data