Static Content API

The Static Content API returns hotel names, images, star ratings, facilities, addresses, and other property details that do not change with availability. Because this data is pre-stored — not fetched live from suppliers — responses are fast and consistent.

GET{baseEndpoint}/api/hotel/content

The parallel call pattern — critical for performance

Call Static Content at the same time as Search Init, not after. This is the most important implementation detail for this API.

Call simultaneously

Static Content API

Returns immediately with hotel names, images, and static details. Your UI can start rendering hotel cards right away.

Call simultaneously

Search Init API

Fires against all configured suppliers and returns a token. Rates come in via polling — they will take longer to arrive.

The result: your users see hotel cards loading immediately while rates stream in behind the scenes. If you call Static Content after Search Init completes, your users see a blank screen while waiting — unnecessary and avoidable.

What the response includes

Hotel nameDisplay name from the supplier

ImagesHero image and gallery

Star ratingOfficial classification

Review ratingGuest score where available

AddressFull property address

Geo-coordinatesLat/long of the property

FacilitiesAmenities and services

Contact infoPhone and email

Nearby attractionsPoints of interest

Matching content to rates on the checkout page

On the checkout page, the content you display must come from the same supplier as the rate the user selected. This is a certification requirement — displaying mismatched content causes discrepancies during booking.

How to do this: Extract the providerName from the rate object in the Rooms & Rates response. Pass it as the providerPrefs parameter in your Static Content API call for the checkout page. This overrides the default content preference configured at the channel level and ensures the property details match the rate source exactly.

Accepted search criteria

The Static Content API accepts the same search criteria as Search Init — circular, polygon, multi-polygon, and hotel ID. Pass the same parameters to both calls when firing them in parallel.

Content is supplier-sourced but stored by ZentrumHub. ZentrumHub pre-fetches and stores static content from all configured suppliers. The relevant supplier's content is returned based on your channel configuration and any providerPrefs you pass.