# RateHawk hotel mapping solutions

> URL: https://hotelmapping.org/en/integrations/ratehawk-hotel-mapping-solutions/ · Language: English

Static hotel data from RateHawk is processed on hotelmapping.org as a ready connector. Hotel IDs, Latin and, where available, Cyrillic names, room names and board information are standardized and linked to a permanent HM ID, so RateHawk records merge into one hotel card with other suppliers.

## About the provider

RateHawk is a B2B hotel booking platform for travel agencies, tour operators and corporate travel companies. It is part of Emerging Travel Group.

Official website: https://www.ratehawk.com

## What data we map

- RateHawk hotel ID → HM ID
- Hotel name (Latin and, where available, Cyrillic spelling) and address
- Coordinates → latitude and longitude selected from supplier records (validation planned)
- Room names → standard room type, class, view, bed
- Board (meal) information → RO, BB, HB, FB, AI, UAI…
- Region and city information → country, province, district, resort area
- Phone, email and website (for scoring)

## Challenges specific to this provider

- **Cyrillic-script names:** The same hotel can arrive in Cyrillic letters in a Russian record and in Latin letters in an English record. Character-by-character comparison counts these records as separate hotels; transliteration and multilingual similarity are needed.
- **Detailed and long room names:** Room names can combine view, bed, floor and room feature information in one line. A rule dictionary and a labeling model work together to separate the room type from this text.
- **Large static data files:** Static content may be provided as bulk files. Processing only the changed records alongside the full file is the practical way to keep mapping up to date.

## Sample output

**GET /v1/suppliers/ratehawk/codes/8812047 (fictional code)**

```json
{
  "supplier": "ratehawk",
  "code": "8812047",
  "supplier_name": "Сансет Бэй Резорт энд Спа",
  "name_latin": "Sanset Bey Rezort end Spa",
  "hm_id": "HM-1048213",
  "name": "Sunset Bay Resort & Spa",
  "destination_id": "TR-07-SERIK-BELEK",
  "confidence": 0.981,
  "matched_at": "2026-11-02T08:14:00Z"
}
```

## Language differences in RateHawk data

Because Turkish and Mediterranean hotels are sold heavily to the Russian-speaking market, the same property can appear in supplier records in Cyrillic and Latin letters, with different spellings. In the example, the record "Сансет Бэй Резорт энд Спа" is linked to the same HM ID as the "Sunset Bay Resort & Spa" records from other suppliers. This process is part of the [hotel mapping](https://hotelmapping.org/en/products/hotel-mapping-solutions/) product; for the general framework, see the [what is hotel mapping](https://hotelmapping.org/en/guide/what-is-hotel-mapping/) guide.

## What gets standardized?

| RateHawk data | Standard output |
| --- | --- |
| Hotel ID | HM ID |
| Cyrillic and Latin name | A single normalized hotel name |
| Room name | Room type, class, view, bed labels |
| Meal information | RO, BB, HB, FB, AI, UAI… |
| Region | Hierarchy in the form `TR-07-SERIK-BELEK` |

## Flow

Static data is received through the ready connector and versioned. Names are converted to Latin script through [transliteration](https://hotelmapping.org/en/glossary/transliteration/), and each record is scored against nearby candidates. Records that are uncertain (0.80–0.97) go to expert review. If you want to query a single hotel on demand, the [Find Match API](https://hotelmapping.org/en/products/find-match-api-solutions/) returns an HM ID and a confidence score from name, address and coordinates.

_Connection status and brand usage will be verified with the provider before launch._

## Frequently asked questions

### How are Russian hotel names matched?

Cyrillic names are transliterated into Latin script and compared using multilingual embeddings. The name alone is not enough; distance, phone and website also feed into the score.

### Does the RateHawk ID replace the HM ID?

No. The RateHawk ID is valid only within the RateHawk system. The HM ID is the permanent identity that merges this ID with other supplier codes for the same hotel; both values return together in the API response.

## Related products

- [Hotel mapping solutions](https://hotelmapping.org/en/products/hotel-mapping-solutions/)
- [Room mapping solutions](https://hotelmapping.org/en/products/room-mapping-solutions/)
- [Find Match API solutions](https://hotelmapping.org/en/products/find-match-api-solutions/)
