---
title: "Booking.com Connectivity vs Expedia Rapid vs Hotelbeds"
description: "Booking.com Connectivity, Expedia Rapid ve Hotelbeds API Suite'i integration topology, inventory ownership, shopping/booking lifecycle ve operational responsibility açısından karşılaştırın."
slug: "booking-connectivity-vs-expedia-rapid-vs-hotelbeds"
translationKey: "compare-booking-connectivity-vs-expedia-rapid-vs-hotelbeds"
locale: "tr"
type: "comparison"
category: "distribution"
tags: ["booking-com","expedia-rapid","hotelbeds","hotel-api","distribution"]
publishedAt: "2026-09-26"
updatedAt: "2026-09-26"
reviewedAt: "2026-09-26"
sources:
  - title: "Booking.com Connectivity APIs"
    url: "https://developers.booking.com/connectivity/docs"
  - title: "Expedia Rapid Lodging"
    url: "https://developers.expediagroup.com/rapid/lodging"
  - title: "Hotelbeds Hotels API"
    url: "https://developer.hotelbeds.com/documentation/hotels/"
---
Bu üç ürün aynı teknik problemi çözmez. Booking.com Connectivity bir **distribution/connectivity** contract'ıdır; Expedia Rapid ve Hotelbeds ise **B2B lodging shopping/booking supply** tarafında konumlanır. Bu yüzden doğru karşılaştırma “hangi API daha iyi?” değil, hangi lifecycle ve ownership modeline ihtiyacınız olduğudur.

## Karşılaştırma matrisi

| Boyut | Booking.com Connectivity | Expedia Rapid | Hotelbeds |
|---|---|---|---|
| Primary rol | Channel connectivity / ARI / reservation delivery | Lodging shopping + booking | B2B lodging supply + booking |
| Inventory ownership | Property/PMS/CM source state → Booking.com | Expedia Group supply contract | HBX/Hotelbeds contracted/aggregated supply |
| Search API | Core use-case değil | Evet | Evet |
| Reprice / validation | Generic search reprice değil | Price Check | CheckRates when RECHECK |
| Booking create | Consumer Booking.com tarafında olur | Rapid Booking API | Booking API |
| Reservation delivery | Booking.com → PMS/CM | Rapid booking lifecycle | Hotelbeds booking lifecycle |
| Pagination/polling | Endpoint/queue specific | Core flow token-link based | Endpoint specific |
| Best fit | Property distribution | OTA/affiliate-style hotel shopping | Bedbank/B2B sourcing |

## Mimari fark

Booking.com Connectivity için source of truth genellikle PMS/CRS/channel manager'dır. Sistem ARI/content state'i Booking.com'a project eder ve reservation state'ini geri alır.

Rapid ve Hotelbeds'te ise buyer-side sistem dış supplier offers'ı search eder, normalize eder, gerekirse revalidate eder ve booking oluşturur.

```text
Connectivity:
PMS/CRS -> ARI/content -> Booking.com
Booking.com -> reservation -> PMS/CRS

Supply API:
Buyer search -> supplier offer -> reprice/check -> booking -> servicing
```

## Ownership ve canonical model

Booking.com tarafında room/rate mapping, sellability, reservation delivery ve acknowledgement öne çıkar.

Rapid/Hotelbeds tarafında canonical hotel/room/offer, supplier reference, price components, cancellation rules, booking reference ve payment ownership öne çıkar.

Bu modelleri tek generic "hotel API adapter" altında aynı lifecycle gibi ele almak abstraction hatası üretir.

## Reprice farkı

Rapid'de selected rate için Price Check transaction boundary'dir. Hotelbeds'te `rateType=RECHECK` ise CheckRates gerekir; `BOOKABLE` doğrudan booking'e gidebilir.

Booking.com Connectivity'de generic metasearch-style search → reprice → book akışı yoktur; distribution state ve inbound reservation lifecycle vardır.

## Failure modes

**Booking.com Connectivity**
- stale ARI,
- mapping drift,
- reservation queue lag,
- ack/persist ordering problemi.

**Expedia Rapid**
- expired booking link,
- price changed,
- sold out,
- unknown booking outcome.

**Hotelbeds**
- stale rateKey,
- missing CheckRates,
- signature/mTLS issue,
- duplicate booking after timeout.

## Ne zaman hangisi?

Property inventory'nizi Booking.com'a dağıtıyorsanız Connectivity gerekir.

Bir hotel-search/OTA/metasearch backend'i için external bookable supply arıyorsanız Rapid veya Hotelbeds daha ilgili ürün ailesidir.

Çoklu-supplier mimaride Rapid ve Hotelbeds aynı canonical Offer contract'ına normalize edilebilir; fakat provider-specific revalidation ve booking semantics adapter içinde korunmalıdır.

## Karar checklist

- [ ] Ben supplier mıyım yoksa buyer mıyım?
- [ ] Inventory source of truth kim?
- [ ] Booking'i kim create ediyor?
- [ ] Reprice/validation zorunlu mu?
- [ ] Reservation delivery mi, supplier booking create mi yönetiyorum?
- [ ] Payment/merchant ownership nerede?
- [ ] Mapping ve reconciliation hangi sistemde?