Hotel factsheet solutions

The hotel factsheet gives a hotel's core information in separate, filterable fields instead of free text: property type, stars, room count, check-in/check-out times, beach and pools, child and pet policy, restaurants and contact details. Information from all suppliers is merged under the hotel's HM ID, conflicting values are flagged, and the data is delivered through the API and dump files.

What you gain

  • Ready for filtering

    Check-in time, child policy, beach type and room count are separate fields, so they can be used directly in filters and comparisons.

  • One hotel, one truth

    A hotel's information from all suppliers is gathered under one HM ID. The hotel page does not change depending on which supplier you came from.

  • Conflicts are visible

    When suppliers give different values for the same field, the field is flagged. You see in the response which information is awaiting review.

  • Consistent with descriptions

    Hotel descriptions are generated from the same factsheet data, so the text and the fields do not contradict each other.

Before and after

Raw property information from two suppliers

supplier_facts.txt
[A / HTL-88213]
Check-in 14:00 / Check-out 12:00. 412 rooms. Private sandy
beach 250m. 3 outdoor pools, 1 indoor pool. Kids 0-6.99 free.
Pets not allowed.

[B / 40917]
Giriş: 15.00, Çıkış: 12.00 - 410 oda - Otele ait kum plaj
(250 mt) - Açık havuz x3 - Çocuk 0-7 yaş arası ücretsiz

Standard factsheet under one HM ID

HM-1048213 factsheet
{
  "hm_id": "HM-1048213",
  "factsheet": {
    "check_in": "14:00",
    "check_out": "12:00",
    "room_count": 412,
    "beach": { "type": "sand", "private": true, "distance_m": 250 },
    "pools": { "outdoor": 3, "indoor": 1 },
    "child_policy": { "free_from_age": 0, "free_to_age": 6.99 },
    "pets_allowed": false,
    "review_flags": ["check_in", "room_count"]
  }
}

Sample data; the hotel and codes do not belong to a real property. Fields where suppliers conflict (here check-in time and room count) are flagged with review_flags.

How it works

  1. 1

    Merging the sources

    Hotel information from all supplier records tied to the same HM ID is brought together. Raw data is stored as is, and changes are versioned.

  2. 2

    Splitting into fields

    Times, numbers, distances and policies in free text are turned into separate fields; time, distance and age formats are standardized.

  3. 3

    Conflict check

    When sources give different information, the values are compared. Uncertain fields are flagged and land in the data team's review queue.

  4. 4

    Delivery and updates

    The factsheet is returned from GET /v1/hotels/{hm_id}/content; the full inventory arrives in daily full and delta dump files.

Why does the factsheet use separate fields?

Suppliers often send hotel information inside free text. One supplier writes check-in as 14:00, another as 15:00; one says 412 rooms, the other 410. Beach information gets lost inside a sentence, and the child age limit arrives in different formats. As it stands, you cannot build a filter for “hotels with a private sandy beach” or “children aged 0-6 stay free”.

The hotel factsheet pulls this information out into separate fields and ties it to the hotel’s HM ID. The precondition is matching the hotel correctly; you can find the method in the hotel mapping guide and the product on the hotel mapping page.

Factsheet fields

Group Fields Sample value
Property details Property type, stars, chain and brand, number of rooms and floors, opening and renovation year Resort, 5 stars, 412 rooms
Policies Check-in/check-out time; child, pet, smoking and payment policy 14:00 / 12:00, ages 0-6.99 free
Beach and pool Beach type, whether it belongs to the hotel, distance; number of outdoor and indoor pools Sand, private, 250 m; 3 outdoor, 1 indoor
Dining Restaurants, bars, cuisines, opening hours Turkish restaurant, pool bar
Contact and address Verified address, phone, email, website [email protected]

Field names and values are language-independent; in your interface you show the label in your own language.

Conflicting information

When suppliers give different values for the same hotel, the values are compared. Fields that remain uncertain are flagged with review_flags and checked by the data team. This way you can see from the response which information is certain and which is awaiting review.

Descriptions and delivery

Hotel descriptions are generated from the same factsheet data; a time or distance mentioned in the text never contradicts the value in the field. The hotel’s photo gallery is handled by the hotel images service; if the factsheet lists a beach but no image is tagged as beach, you can raise a warning for your content team.

The factsheet is delivered per hotel through the REST API and for the whole inventory through daily full and delta dump files. The include parameter and field names in the example are an API v1 draft; the final schema will be published on the developers page. For coverage and pricing, you can request a quote.

What is hotel mapping? The complete guide

API example

Request

Factsheet request
curl "https://api.hotelmapping.org/v1/hotels/HM-1048213/content?include=factsheet" \
  -H "X-API-Key: $HM_API_KEY"

Response

200 OK
{
  "hm_id": "HM-1048213",
  "factsheet": {
    "property": { "type": "resort", "stars": 5, "room_count": 412 },
    "policies": {
      "check_in": "14:00",
      "check_out": "12:00",
      "child_policy": { "free_from_age": 0, "free_to_age": 6.99 },
      "pets_allowed": false
    },
    "beach": { "type": "sand", "private": true, "distance_m": 250 },
    "pools": { "outdoor": 3, "indoor": 1 },
    "dining": [
      { "type": "restaurant", "cuisine": "turkish" },
      { "type": "bar", "location": "pool" }
    ],
    "contact": { "email": "[email protected]" },
    "review_flags": ["check_in", "room_count"]
  },
  "updated_at": "2026-11-02T08:14:00Z"
}

Code samples are illustrative; field names may change in the v1 release.

Frequently asked questions

What is a hotel factsheet?

It presents a hotel's core information (property type, stars, room count, check-in/check-out times, policies, dining, contact) as structured fields.

What is the difference between the factsheet and a hotel description?

A description is text written to be read; the factsheet is a set of separate fields for filtering and comparison. Both rest on the same verified data.

Which value is used when suppliers give different information?

The values are compared; fields that remain uncertain are flagged and checked by the data team. The response shows which fields are awaiting review through review_flags.

In which formats can I get the factsheet data?

Per hotel through the REST API, or for the whole inventory through daily full and delta dump files (CSV, JSON). A webhook for change notifications is planned.

Request a quote

Get your tailored quote

Send your request in three steps; we will email the quote to your work address. The request is non-binding.

  1. 1 Select solutions
  2. 2 Select suppliers
  3. 3 Leave your contact details