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–90+ seconds | Confirmation can take a minute; platform book floor is 90s |
| 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 a few seconds above your settings.timeout, and implement retry with backoff only for idempotent reads or documented safe cases—not blindly on POST /booking. Prefer errors[].additionalData.recommended_action when present (Error handling).
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
settings.timeout is in milliseconds. Recommended buyer values:
| Operation | Recommended | Platform behaviour |
|---|---|---|
| Search / availability | ≥ 8000 (prefer 10000–15000 with many connections) | Aggressive 1–3s budgets often return empty / trip breakers before suppliers answer |
| Quote | ≥ 5000 | Usually faster than search |
| Book | ≥ 92000, or omit for the connection ceiling (~2 minutes) | Values below 90000 are raised to that floor |
| Cancel | Prefer matching book-scale budgets when in doubt | Same confirmation-style risk as book on some suppliers |
If your HTTP client times out while Bundleport is still confirming, the booking may exist without a reference on your side — reconcile with booking list and clientReference; see Create a booking.