Skip to main content
Hotel and room type responses include responsive image metadata. Room types embedded in hotel responses use the same image shape.

​
Response shape

Every image contains all six fields:

​
Build a responsive image

Use only the variant URLs returned by the API. Do not construct a URL for a missing width. Images are never enlarged, so an 1100-pixel original has w480 and w960, but no larger variants.
Set srcset only when the resulting string is non-empty. Set sizes to the actual layout slot, for example (max-width: 768px) 100vw, 50vw. The browser then selects the best available variant for the viewport and device pixel density. Use non-null width and height as the HTML intrinsic dimensions. They reserve the correct aspect ratio before the image loads. Do not replace them with the CSS slot size.
Use loading="eager" and fetchpriority="high" only for the single image that is the page’s likely largest contentful paint (LCP). Lazy-load images outside the initial viewport.

​
Empty variants and fallbacks

An empty variants object means that no responsive variant is available. It does not mean that processing is still pending. Omit srcset and use thumbnailUrl ?? url as src. There are two possible cases:
  • A small original can have known width and height but no variant because its width is below 480 pixels.
  • An unavailable legacy image has width: null, height: null, and variants: {}.
As a final error fallback, remove srcset and switch src to thumbnailUrl ?? url. This is useful if a cached client encounters a missing variant, but it does not replace normal HTTP error monitoring.

​
Alternative text

alt follows Accept-Language. The response contains the requested locale keys:
  • A missing or null hotel image translation falls back to the localized hotel name.
  • A missing or null room image translation falls back to the localized room category, or null when that category translation is unavailable.
  • An explicit empty string remains "". Preserve it when the image is decorative.
  • A non-empty stored value is trimmed.
The API provides recommended alternative text. Your client can still use alt="" when the image is decorative or redundant in its rendered context.

​
Compatibility

The image fields are additive in API v2. Existing url and thumbnailUrl values retain their behavior, and thumbnailUrl remains present as a nullable field throughout API v2. API v1 image responses are unchanged. See the Hotel and Room type object references for entity-specific behavior.