Performance & Availability
This page describes orientation values for planning integrations. Contractual SLAs may differ for enterprise agreements—confirm with your account team if you need committed numbers.
Availability
Bundleport targets high availability for the API gateway and core hotel services. For current operational status, use your organization’s status page link (if provided in onboarding) or contact support@bundleport.com for the public status URL.
Incident communication for production typically includes email or dashboard notices according to your support tier.
Typical response times (indicative)
Latencies depend on provider count, search breadth, and network conditions. Orders of magnitude:
| Operation | Typical range | Notes |
|---|---|---|
| Content catalog reads | Sub-second to a few seconds | Cached catalog data where applicable |
| Availability search | ~2–15+ seconds | Dominated by slowest supplier in connectionCodes; parallel queries |
| Quote (prebooking) | ~2–10 seconds | Single-option recheck |
| Book | ~5–60+ seconds | Some suppliers require longer client timeouts for confirmation; use settings.timeout and expect platform-side minimums for certain connections |
| Booking detail / list | ~1–5 seconds | Depends on filters and volume |
| Cancel | ~2–15 seconds | Varies by supplier and policy |
Always configure client-side timeouts above your settings.timeout where possible, and implement retry with backoff only for idempotent reads or documented safe cases—not blindly on POST /booking.
Rate limits
Per-key limits are enforced at the gateway. Defaults and configuration are described in Rate limits. High-volume integrations should monitor response headers and request limit increases through support or account settings.
Timeouts and settings.timeout
You can set settings.timeout (milliseconds) on transactional requests. The platform may apply minimum timeouts for specific supplier integrations (for example, booking confirmation). If your timeout is too low, you may see client-side timeouts while a booking still completes server-side—use booking list and clientReference to reconcile; see Create a booking.