UK travel agencies and tour operators evaluating bed bank connectivity consistently encounter Hotelbeds as one of the three dominant wholesale hotel suppliers in the market — alongside Stuba and TBO — but the practical details of how a Hotelbeds API integration works, what it costs, and what UK regulatory requirements it touches are rarely explained in a single place. Building a direct Hotelbeds API integration from scratch is a substantial development project; accessing Hotelbeds inventory through a pre-integrated booking platform is significantly faster and lower cost. This guide covers both options, explains the Hotelbeds API structure in practical terms, and addresses the UK compliance requirements that apply when Hotelbeds hotel content is combined with flight content for dynamic packaging.
What Is Hotelbeds API Integration?
Hotelbeds API integration is the technical process of connecting a travel agency’s booking platform or website to Hotelbeds’ wholesale hotel inventory via their published REST API, enabling real-time hotel availability search, net rate pricing retrieval, booking creation, and cancellation management without accessing Hotelbeds’ own booking interface. Hotelbeds is one of the world’s largest hotel bed banks, providing access to over 200,000 properties globally at net wholesale rates — rates that the agency then marks up to create a consumer or trade-facing price. For UK travel agencies and tour operators, a Hotelbeds integration is the primary mechanism through which wholesale hotel content is fed into a B2B agent portal, a consumer IBE, or a dynamic packaging engine — replacing the need to contract individual hotels directly or use higher-cost retail channels.
Why Hotelbeds API Integration Matters for UK Travel Agencies
1. Wholesale Rates Deliver Better Margins Than Retail Channels
Hotelbeds’ net rates are typically 15–35% below published retail rates for the same properties, giving UK agencies room to apply markup while remaining price-competitive against direct booking channels. A UK OTA that sources hotel inventory from Hotelbeds at net rates and applies a 20% markup can price the same room below the hotel’s own website rate in many markets — particularly in Mediterranean, Caribbean, and Asian destinations where Hotelbeds has deep contracted inventory. Retail-rate hotel aggregators (such as OTA APIs with affiliate pricing) do not provide this margin structure — the agency effectively earns commission rather than controlling markup.
2. Single API Replaces Hundreds of Individual Hotel Contracts
UK tour operators that contract hotels directly must negotiate individual agreements with each property — a process that takes months per hotel and produces pricing valid only for the contracted period. A Hotelbeds integration provides access to over 200,000 properties through a single API contract and a single technical connection. The operational saving is significant: one supplier relationship to manage, one invoicing cycle, one data feed to maintain, versus hundreds of individual hotel relationships each requiring separate rate loading, availability management, and invoice reconciliation.
3. Global Coverage Fills Long-Tail Destination Gaps
UK tour operators with a focused destination portfolio — say, Mediterranean beach holidays — can use Hotelbeds to fill long-tail requests for destinations they do not contract directly, without adding supplier complexity. When a customer asks for a hotel in a destination outside the operator’s direct contract portfolio, Hotelbeds inventory provides a bookable option rather than a declined enquiry. According to ABTA, UK consumers increasingly expect agencies to fulfil requests across a broader destination range than agencies can economically contract directly — bed bank connectivity is the standard solution.
4. Dynamic Packaging Requires Bed Bank Connectivity
Any UK agency building a dynamic packaging capability — combining live GDS flight content with hotel availability at the point of sale — requires a bed bank API as the hotel content layer. GDS hotel content covers corporate chains well but is not the primary source of net-rate holiday accommodation for leisure travel. Bed banks including Hotelbeds are the standard hotel inventory source for UK tour operators building dynamic package products for the leisure market. For the full architecture of a dynamic packaging engine, see our B2B vs B2C travel booking engine guide.
Hotelbeds API Integration: Technical Guide for UK Travel Developers
Step 1: Obtain a Hotelbeds API Account and Credentials
UK agencies apply for Hotelbeds API access through the Hotelbeds Marketplace portal. New applicants must provide business registration details, ABTA or ATOL licence information, and projected booking volumes. Hotelbeds operates a sandbox (test) environment and a production environment — API credentials are issued separately for each. Sandbox access is typically granted within five to ten working days of a complete application; production access follows completion of the commercial contract and rate schedule negotiation.
Step 2: Understand the Hotelbeds API Architecture
The Hotelbeds Hotel API is a REST API that uses JSON for all requests and responses. Authentication uses an API key and secret, combined to generate a SHA-256 signature passed in the request header on every call. The core workflow covers four primary endpoints: hotel availability search, hotel rates check (used to confirm pricing before display), booking creation, and booking cancellation. A fifth endpoint — hotel content — returns static hotel information (name, location, images, amenities) and is typically called less frequently as content caches can be refreshed daily rather than on every search.
Step 3: Implement Hotel Availability Search
The availability search endpoint accepts a destination (as a Hotelbeds destination code, or a latitude/longitude with radius), check-in and check-out dates, occupancy details, and optional filters including star rating, board basis, and maximum rooms. Responses return a list of available hotels with room type options, board basis variants, and net rate pricing for each option. For a UK agency displaying prices in GBP, conversion from the net rate currency (often EUR or USD) must be applied before display — Hotelbeds returns rates in the currency agreed in your contract, not automatically in GBP. Always apply a currency buffer — a small additional markup to cover exchange rate movement between the search and the booking confirmation.
A minimal availability request:
| POST https://api.hotelbeds.com/hotel-api/1.0/hotels Api-key: YOUR_API_KEY X-Signature: SHA256(api_key + secret + unix_timestamp) Accept: application/json Accept-Encoding: gzip { “stay”: { “checkIn”: “2026-08-15”, “checkOut”: “2026-08-22” }, “occupancies”: [{ “rooms”: 1, “adults”: 2, “children”: 0 }], “destination”: { “code”: “PMI” }, “filter”: { “minCategory”: 3, “maxCategory”: 5 } } |
Step 4: Implement the CheckRates Endpoint Before Booking
The CheckRates endpoint must be called after a customer selects a hotel and room type — before presenting the final price and before creating a booking. Hotelbeds net rates can change between the availability search and the booking moment — the CheckRates call returns the current confirmed rate, cancellation policy, and any rate-specific conditions. For UK agencies operating under the UK Package Travel Regulations 2018, the price presented to the consumer before payment must match the price charged — the CheckRates call is the mechanism that confirms this before the booking is finalised. Never skip the CheckRates step to save an API call — rate changes between search and booking are common, particularly in high-demand periods.
Step 5: Create a Booking
The booking creation endpoint accepts the rate key returned by CheckRates, passenger details for the lead traveller, and payment confirmation. Hotelbeds operates on a pre-pay model for most rates — the agency pays Hotelbeds at the time of booking and collects payment from the consumer or agent separately. The booking response returns a Hotelbeds booking reference, hotel confirmation details, and cancellation policy specifics. Store the Hotelbeds booking reference against your internal booking record — it is required for all subsequent management calls including amendments and cancellations.
Step 6: Implement Cancellation and Amendment Workflows
The cancellation endpoint accepts the Hotelbeds booking reference and returns the applicable cancellation charge based on the policy associated with the rate at time of booking. Cancellation policies vary by rate type — some Hotelbeds rates are fully flexible with no charge up to 24 hours before check-in; others are non-refundable from the moment of booking. Your booking platform must display the cancellation policy to the agent or consumer before they confirm the booking — this is both a Hotelbeds contractual requirement and a UK Package Travel Regulations 2018 obligation for package bookings. Amendment functionality (date changes, occupancy changes) is available through the Hotelbeds API for some rate types but requires a cancellation and rebook workflow for others — confirm the amendment capability for each rate type before presenting amendment options to your users.
Step 7: Handle Errors, Rate Limits, and Caching
Hotelbeds API responses use standard HTTP status codes — 200 for success, 400 for invalid request parameters, 401 for authentication failures, and 500 for Hotelbeds server errors. Rate limits apply in production: availability search calls are capped per second and per minute, with limits confirmed in your API contract. Implement a hotel content cache — refreshed daily — for static hotel data (descriptions, images, amenities) to avoid calling the content endpoint on every search and stay within rate limits. Availability search responses should not be cached — hotel availability changes in real time and a cached availability result may produce a failed booking if the inventory has moved.
| Hotelbeds API Core Capabilities at a Glance ▶ Hotel availability search by destination, lat/long, or hotel code — returns net rates per room type ▶ CheckRates — confirms current net rate and cancellation policy before booking ▶ Booking creation — pre-pay model; returns Hotelbeds reference and hotel confirmation ▶ Booking cancellation — applies rate-specific policy; returns applicable charge ▶ Hotel content API — static property details, images, amenities, location data ▶ Booking list / status — retrieves all bookings within a date range for reconciliation ▶ Voucher generation — produces hotel vouchers for ATOL and non-ATOL bookings ▶ Multiple currencies — rates returned in contracted currency; GBP conversion applied by agency |
Hotelbeds vs Competing Bed Banks: UK Agency Comparison 2026
| Bed Bank | API Type | Inventory Depth | Pricing Model | Best Fit for UK Agencies |
| Hotelbeds | REST API (JSON) | 200,000+ hotels globally; strong European and Mediterranean coverage | Net rate — agency applies markup | UK OTAs and tour operators needing broad global inventory at wholesale rates |
| Stuba | REST API (XML/JSON) | Strong Caribbean, Florida, and long-haul coverage; UK B2B focus | Net rate — trade-only, no direct consumer access | UK B2B consolidators and package operators focused on long-haul and Caribbean |
| TBO Holidays | REST API (XML/JSON) | Asia-Pacific, Middle East, and India coverage; growing European portfolio | Net rate with agency markup | UK operators with significant Asia-Pacific and Middle East product portfolios |
| Booking.com for Business | REST API | Broad global coverage; consumer pricing adjusted for B2B | Adjusted consumer rate — not wholesale net | Agencies needing long-tail property coverage; less competitive on popular routes |
| GDS Hotel Content (Travelport/Sabre) | GDS native API or adapter | Corporate and published hotel rates; chain hotels well-covered | Published or negotiated corporate rates | UK TMCs and corporate travel agents needing GDS-linked hotel settlement |
| Direct hotel XML connections | Varies per property | Deep single-property or small-group inventory | Direct contract negotiated | High-volume operators contracting specific hotel groups or resort chains directly |
UK-Specific Considerations for Hotelbeds API Integration
ATOL and Dynamic Packaging with Hotelbeds Content
When Hotelbeds hotel content is combined with GDS flight content at the point of sale to create a dynamic package, the organiser becomes liable under the UK Package Travel Regulations 2018 and must hold ATOL from the Civil Aviation Authority. ATOL certificates must be generated at point of booking — your booking platform, not Hotelbeds, is responsible for this documentation. Hotelbeds’ own voucher generation does not constitute ATOL documentation — your platform must generate ATOL certificates separately using your own ATOL licence number. Confirm with your ATOL compliance adviser which entity is the organiser when Hotelbeds hotel content is packaged with GDS flights in your specific booking workflow.
UK Package Travel Regulations 2018 and Pre-Contractual Information
Any dynamic package incorporating Hotelbeds hotel content must present Schedule 1 pre-contractual information to the consumer or agent before the booking is confirmed. This includes the hotel’s name, category, location, board basis, and cancellation policy — all of which are available from the Hotelbeds API but must be formatted by your booking platform into the PTR 2018-compliant pre-contractual information display. The Hotelbeds CheckRates response returns the applicable cancellation policy in machine-readable format — your platform must translate this into consumer-readable terms before the booking step.
UK GDPR and Passenger Data Sent to Hotelbeds
Booking creation calls to the Hotelbeds API include passenger name and contact details — personal data governed by UK GDPR. Your data processing agreement must cover the transfer of personal data to Hotelbeds as a data processor. Confirm that Hotelbeds processes personal data within the UK or EEA, or that appropriate international transfer safeguards are in place under your API contract. Do not transmit passport numbers or payment card data to Hotelbeds unless specifically required by the API documentation and your contract — the minimum necessary data principle applies to all third-party data transfers.
GBP Pricing and Currency Management
Hotelbeds typically invoices UK agencies in EUR for European properties and USD for long-haul destinations. Your booking platform must convert net rates to GBP for display and apply a currency buffer — typically 2–5% — to protect against exchange rate movement between the search, CheckRates, and settlement. The GBP price displayed to the consumer at the search stage must match or be confirmed by the CheckRates-derived price before payment — the Consumer Contracts Regulations prohibit charging more than the price displayed before the consumer commits to purchase. Configure your platform’s currency management before going live, not as a post-launch correction.
PCI DSS for Payment Settlement with Hotelbeds
Hotelbeds operates a pre-pay model — the agency’s payment card or credit account is charged at the time of booking creation, not at consumer check-in. If your platform stores or processes payment card data for Hotelbeds settlement, this is in scope for PCI DSS compliance. The most practical approach is to configure Hotelbeds settlement through a pre-approved credit line on your Hotelbeds account rather than individual card transactions per booking — this removes per-booking card processing from your PCI DSS scope. PCI DSS Level 1 certification standards are available at pcisecuritystandards.org.
How SoftCloudTec Delivers Hotelbeds Connectivity for UK Agencies
| SoftCloudTec’s B2B booking platform and consumer IBE include a pre-built Hotelbeds API integration — alongside connections to Stuba and TBO — eliminating the development cost and timeline of building a direct bed bank connection from scratch. The Hotelbeds connection is activated against the UK agency’s own API credentials within the SoftCloudTec platform, with net rate retrieval, GBP markup application, CheckRates-confirmed pricing, and ATOL certificate generation all handled within the booking flow. UK agencies can combine Hotelbeds hotel content with GDS flight content from Travelport or Sabre for dynamic packaging, with PTR 2018 pre-contractual information generated automatically at the correct booking stage. Most UK agencies go live with Hotelbeds content within 14 days of contract signing. Book a free demo at softcloudtec.com/contact-us/ |
Frequently Asked Questions
| Q: What is Hotelbeds API integration and what does it give a UK travel agency access to? Hotelbeds API integration connects a UK agency’s booking platform to Hotelbeds’ wholesale hotel inventory via a REST API, giving the agency access to real-time availability, net wholesale rates, and booking capability for over 200,000 properties globally. The agency applies its own markup to the net rates before displaying prices to agents or consumers. The integration replaces the need to contract hotels individually or use retail-price channels, delivering better margins and broader destination coverage from a single supplier relationship. |
| Q: Do I need ATOL to sell Hotelbeds hotel content to UK consumers? Hotelbeds hotel-only bookings do not require ATOL — ATOL covers flight-inclusive packages only. However, if you combine Hotelbeds hotel content with a GDS flight at the point of sale, you are dynamically creating a package under the UK Package Travel Regulations 2018, and ATOL becomes mandatory before you take a single flight-inclusive booking. The ATOL certificate must be generated by your booking platform — not by Hotelbeds — using your own ATOL licence number from the Civil Aviation Authority. |
| Q: How much does Hotelbeds API access cost for a UK travel agency in 2026? Hotelbeds does not charge a direct API access fee — revenue is generated through the net rate margin on each booking, not a platform licence. However, UK agencies must meet minimum booking volume commitments to retain API access, and the commercial terms of the net rate contract — including the margin Hotelbeds takes between wholesale cost and net rate — are negotiated at the time of account setup. Accessing Hotelbeds through a pre-integrated booking platform (rather than building a direct integration) avoids a development cost of £15,000–£60,000 for the API connection itself. |
| Q: What is the difference between Hotelbeds, Stuba, and TBO for UK agencies? Hotelbeds offers the broadest global hotel inventory with particular depth in Mediterranean, European, and worldwide city hotel markets — the primary choice for UK OTAs and tour operators needing wide geographic coverage. Stuba is a UK-focused trade-only bed bank with particularly strong Caribbean, Florida, and long-haul product — commonly used by UK B2B consolidators and package operators. TBO has strength in Asia-Pacific, Middle East, and India markets. Most UK operators with a broad destination portfolio connect to at least two of the three to ensure coverage gaps are filled. |
| Q: How do I ensure the Hotelbeds CheckRates step is correctly implemented in my booking flow? The CheckRates endpoint must be called after the customer selects a hotel and room type from the availability results, and before the booking creation call is made. The rate key from the availability search response is passed to CheckRates, which returns the current confirmed net rate and applicable cancellation policy. If the rate has changed since the availability search, your platform must display the new rate to the customer before proceeding. Never cache availability rates and use them directly for booking — always call CheckRates to confirm the current rate. |
| Q: Does SoftCloudTec include a pre-built Hotelbeds integration or must it be developed separately? SoftCloudTec includes pre-built connections to Hotelbeds, Stuba, and TBO within its B2B platform and consumer IBE subscriptions — the integration does not require any custom development. UK agencies activate their own Hotelbeds API credentials within the SoftCloudTec platform, and the availability search, CheckRates, booking creation, and cancellation workflows are fully handled by the platform. Combined with the GDS integrations to Travelport and Sabre, this gives UK agencies access to both flight and hotel content for dynamic packaging within a single platform subscription. |
Key Takeaways on Hotelbeds API Integration for UK Travel Agencies
For UK travel agencies looking to access wholesale hotel content in 2026, a Hotelbeds API integration delivers global inventory at net rates through a single supplier relationship — replacing the commercial and operational overhead of contracting properties directly. The technical implementation requires careful attention to three stages that UK agencies most commonly handle incorrectly: CheckRates confirmation before booking, GBP currency conversion with an adequate buffer, and ATOL certificate generation when Hotelbeds hotel content is combined with GDS flights for dynamic packaging. Agencies that access Hotelbeds through a pre-integrated booking platform rather than building a direct connection typically go live in under three weeks rather than three months, at a fraction of the custom development cost.