Overview

Introduction

The Hotels Content API provides descriptive information about hotels, including standardised attributes, amenities, policies, and media. You can use it to add hotel details to price and availability results so users can make informed booking decisions. Note that this API does not return prices or availability.

How we use it at Skyscanner

We use the Hotels Content API to render static information on hotel pages, including:

• Hotel name and alternative names
• Address and coordinates (for maps)
• Descriptions and images
• Amenities badges
• Check-in/out times
• Policy information (children, pets, breakfast, payment options)

For reference, here is a Skyscanner Hotels page that showcases these attributes.

Endpoints

This API has 1 endpoint – /content.

/content

POST https://partners.api.skyscanner.net/apiservices/v1/hotels/content

The /content endpoint returns static, descriptive content for one or more hotels.

Concepts

Static content (no prices)

• This API returns static content only.
• If you need pricing or bookable offers, use the Hotels Live Prices API.

Localisation and normalisation

• Many text fields are locale-specific. Provide locale to receive localised content where available. See the Culture API for supported locales.
• Enumerated values (e.g. amenities, accommodation type, star ratings) are normalised across suppliers.

Request

/content

Required fields

Field name	Description
hotelIds	List of hotel IDs to fetch content for. E.g.: 46948122
locale	Locale for localised content. E.g.: en-GB

Response /content

Fields

The response contains a map of hotelId to a hotelsContent object.

Key attributes within hotelsContent are:

Attribute	Description
hotelId	Skyscanner hotel identifier.
hotelName	Localised hotel name (in the requested locale).
hotelNameEn	English hotel name, provided as a fallback.
chainGroup	Hotel chain or group, where applicable.
stars	Normalised star rating.
accommodationType	Enumerated accommodation type (e.g. hotel, hostel, apartment).
hotelStreetAddress	Street address.
hotelPostcode	Postal/ZIP code.
coordinates	Latitude/longitude of the property.
hotelPhone	Primary contact phone number.
hotelEmail	Contact email address, when available.
checkinTime	Typical check‑in time window.
checkoutTime	Typical check‑out time window.
hotelDescription	Localised descriptive text about the property.
images	Array of image objects (URLs, captions, categories).
amenities	Normalised list of amenity codes/labels.
hotelPolicyInfo	Policy info: beds, pets/children, breakfast (options/times/charges/menus), payment methods, important notices (city/hotel), transfers.

For the complete schema (including nested messages and enums), refer to the corresponding API reference.