Documentation

Content Integration

The Bundle API focuses on the booking lifecycle and does not expose catalog content such as hotel descriptions, hotel images, activity modalities, destinations, pickup points, categories, boards, or any other static reference data. To enrich availability and booking responses with that content, integrate with each product's dedicated.

Content API.

Content APIs are independent of the Booking APIs and are designed to be consumed asynchronously — typically on a scheduled synchronization basis rather than per-request, since catalog data changes infrequently.

Hotels

The Hotel Content API returns the hotels master data, images, facilities, boards, categories, chains, segments, countries, destinations, zones, and any other reference information needed to describe a hotel property.

https://developer.hotelbeds.com/documentation/hotels/content-api/

Activities

The Activities Content API returns the activities catalog, modalities, countries, destinations, segments, languages, currencies, highlights, and any other reference information needed to describe an activity.

https://developer.hotelbeds.com/documentation/activities/content-api/overview/

Transfers

The Transfers Content API returns pickup and drop-off locations, routes, destinations, vehicle types, categories, countries, and any other reference information needed to describe a transfer.

https://developer.hotelbeds.com/documentation/transfers/content-api/overview/

Recommended workflow

1. Synchronize the content from each product's Content API on a scheduled basis.
2. Store the catalog data locally in your platform.
3. Use the stored content to decorate the lightweight responses returned by the Booking APIs (Hotels Availability, Activities Availability, Transfers Availability, and the Multiproduct booking endpoints), which return codes and minimal information in order to keep payloads compact.