Content API

The Content APIs give you the hotel data you need to build your search and detail pages — property names, images, star ratings, facilities, room information, and more. In Zentrum Connect, content is a one-time sync, not a live call. You fetch it, store it at your end, and serve it yourself at search time.

This is different from how content works in the Booking Engine, where ZentrumHub serves it dynamically. In Connect, you own your content database. ZentrumHub provides the data via two APIs — one to get the hotel IDs for each supplier, and one to fetch the full property details for those IDs.

How content sync works

Content sync is a two-step process. Run both steps on a regular schedule — daily or weekly depending on how often your suppliers update their inventories.

Step 1

Get Hotel IDs
GET /hotelcontent/ids

→

Step 2

Get Hotel Content
GET /hotelcontent

→

Your database

Store and serve at search time

First, pull the list of hotel IDs available for a supplier under your account. Then, for each batch of IDs, call the content API to fetch the full property record and write it to your database. That database is what your platform uses when displaying search results and hotel detail pages.

Full sync vs delta sync

The Get Hotel IDs API accepts a lastSyncDate and an idType parameter — together these control whether you are doing a full sync or an incremental update.

For your very first sync, set lastSyncDate to 2001-01-01 and idType to New. This pulls everything. After that, use your last successful sync date to fetch only what has changed.

New

Hotel IDs added since your last sync date. Fetch content for these and add them to your database.

Modified

IDs whose content has changed. Re-fetch content for these and update your records.

Removed

IDs no longer available from this supplier. Remove these from your database so you don't show unavailable hotels.

⚠️ Run delta syncs in this order: Removed → Modified → New. Doing it in this sequence keeps your database consistent and avoids showing hotels that have been delisted.

Pagination

The Get Hotel IDs API returns 1000 IDs at a time. If the response includes a nextKey value, there are more IDs available — pass it in your next call to fetch the next page. Keep paginating until no nextKey is returned.

Fetching content

Once you have your hotel IDs, call Get Hotel Content in batches of up to 50 IDs per request. The response for each hotel includes everything you need to display it to users.

Name & addressProperty name, full address, and geo-coordinates

ImagesHero image and full gallery with URLs and captions

Star ratingOfficial classification and guest review scores

FacilitiesProperty-level amenities — pool, gym, Wi-Fi, and more

RoomsStatic room info — bed types, max occupancy, room images, and room facilities

PoliciesCheck-in/check-out times, pet policy, smoking policy

DescriptionsEditorial property descriptions by type

Nearby attractionsPoints of interest with distances

💡 Tip for large inventories: Some suppliers have millions of properties. Process content in batches of 50, write to your database between batches, and spread the initial sync across multiple runs if needed. Use delta sync after that — you won't need to re-download everything each time.

API endpoints

GET https://hotel-connect.prod.zentrumhub.com/api/v1/hotelcontent/ids

GET https://hotel-connect.prod.zentrumhub.com/api/v1/hotelcontent

Full parameter details for both endpoints are available in the API Reference.