WebBeds Marketplace: B2B Bedbank and Distribution Profile

WebBeds describes itself as a global B2B travel marketplace that aggregates accommodation and ground-service supply and distributes that inventory to travel buyers. Buyers can connect through API integration or use trade-only booking interfaces.

Scope

The public corporate material explains the marketplace and connectivity model rather than exposing a fully open developer portal. API details, credentials, commercial terms and implementation specifications are therefore partner-access concerns and should not be inferred from marketing pages.

Supply and buyer sides

Hotels and other suppliers distribute inventory through WebBeds, while travel buyers such as OTAs, agents, corporate travel companies and other sellers consume that inventory.

This two-sided model is important architecturally because supplier identity, buyer contract and downstream resale context can all affect the offer lifecycle.

Integration interpretation

An aggregator integrating a bedbank should preserve:

• bedbank property and room identifiers,
• original rate/booking references,
• cancellation and payment terms,
• taxes and fees,
• booking status and amendments,
• source observation timestamps.

Cross-provider mapping should happen in a canonical hotel layer, not by replacing WebBeds IDs with internal IDs.

DOTW historical context

Destinations of the World (DOTW) should be treated as historical WebBeds context rather than a separate current platform. WebBeds' official company history records:

• 2018: WebBeds acquired DOTW, a Dubai-headquartered B2B business.
• 2019: WebBeds unified its B2B brands under the WebBeds brand as part of a single global technology strategy.

Legacy datasets, supplier references or old integrations may still contain DOTW naming. Preserve that lineage for migration/reconciliation, but do not present DOTW as a separate current distribution platform.

Public documentation boundary

WebBeds publicly states that API connectivity is available to travel buyers, but detailed partner API specifications are not presented as an open self-service developer catalog in the same way as Hotelbeds or Sabre. That distinction should remain visible in a directory rather than implying unverified API behavior.

Operational risks

Bedbank integrations commonly face property duplication, room/rate mapping differences, stale availability and booking-state reconciliation challenges. These are architecture concerns independent of any one provider's private implementation details.

Meta Search interpretation

WebBeds extends the platform directory beyond consumer metasearch and public APIs into wholesale B2B distribution. It is relevant when tracing where hotel inventory originates before it appears in OTA or metasearch comparison layers.