Hospitality API: The Five Kinds of Hotel API, How Access Works, and Which One Answers Your Question

A hospitality API is how one hotel system talks to another: the property management system to the channel manager, the booking engine to the payment provider, the revenue tool to the market data it needs.
Every vendor pitch says "it has an API," and the phrase covers five different things with five different access models.
The catch for a hotel team is that four of the five kinds are about your own hotel.
The PMS knows your rooms, the channel manager knows your rates, the booking engine knows your guests, and none of them knows what the hotel across the street charged last night.
This guide maps the five kinds in plain language, walks through how a PMS API is actually accessed using Oracle's OHIP and an open-API PMS as examples, and covers the fifth kind, market data, with a live example.

Key Takeaways

• Hospitality APIs come in five kinds. PMS, distribution, booking engine and payments, guest-facing, and market data. Each moves different data and is accessed differently.
• A PMS API is granted by the hotel. Vendors register on the PMS developer portal, build against a sandbox, and go live only when a hotel approves the connection.
• The integration marketplace is the API made visible. A PMS with an open API shows up as hundreds of pre-built connections; a closed one shows up as a services quote.
• Four of the five kinds only know your hotel. Competitor rates, direct-versus-OTA spreads, and reviews across booking sites come from market data APIs.
• Market data needs a key, not a project. A hotel data API returns the public prices and reviews of any hotel on request, and a spreadsheet can be the client.

The Five Kinds of Hospitality API

Two of these get confused constantly.
A PMS API and a distribution API both carry rates, in opposite directions: the PMS API is how tools read and write your hotel's data, and the distribution API is how your rates leave the building for the OTAs.
Our hotel booking API guide covers the distribution and booking side from the seller's point of view, including who qualifies for each supplier's program.
The fifth row is the odd one out.
It doesn't touch your systems at all, which is why it's the only kind a hotel can adopt in an afternoon.

How a PMS API Works: OHIP and the Open-API PMS

The clearest way to understand a hospitality API is to watch one being accessed.
Oracle's OHIP.
Oracle Hospitality Integration Platform is the API layer for OPERA Cloud, the most widely deployed PMS in larger hotels, and its specifications and Postman collections are published on GitHub under an open license, with a companion workspace of more than 2,200 sample API messages.
Oracle's own documentation describes access as a four-step process: obtain details from the hotel (the partner sandbox uses the hotel code SAND01), add an environment with its gateway URL and credentials, obtain an OAuth token from that gateway, and call the APIs.
Step one is the sentence that matters for a hotel manager: the vendor gets nothing until a hotel provides its environment details, which is the approval.
An open-API PMS.
Cloud PMS vendors built after the API era go further.
Mews, for example, states that its open API "allows external systems to connect directly with Mews" with "full access to core platform functionality," splits it into four APIs (Connector, Channel Manager, Booking Engine, and Point-of-Sale), and lists more than 1,000 pre-built integrations in its marketplace.
What this means in practice:

The non-technical takeaway: a PMS API is a door the hotel holds the key to, and the vendors do the building.

What a Hospitality API Is Not

An API isn't a feature you click.
It's a documented way for another system to ask for data or send it, and the visible result is an integration built by someone.
Three things follow.
"Has an API" says nothing about what the API allows.
A PMS whose API exposes reservations but not rates can't feed a revenue tool; the scopes matter more than the checkbox.
The integration marketplace is the API's report card.
Hundreds of pre-built connections mean the API is open, documented, and used; a services quote for each connection means it isn't.
Documentation you can read before you buy is the tell.
Oracle publishes specs on GitHub and open-API PMS vendors publish docs sites, and a vendor whose API docs need a sales call is telling you something about the access model.
The questions to ask: what can it read, what can it write, who approves a connection, and where are the docs.

The API Most Hotels Don't Have: Market Data

Every kind above knows your hotel from the inside.
The question a revenue manager asks each morning ("what are the five hotels around me charging tonight, and what are their guests saying") isn't answerable from any of them.
Market data APIs exist for that question.
They read the public booking sites (the same pages a traveler sees) and return the rates, availability, ratings, and reviews of any hotel as structured data, on request, with no connection to the hotel's systems because nothing on the page is private.
StayAPI is one of them, covering Booking.com, Expedia, Google Travel, TripAdvisor, and chain websites under one key.
Here's the kind of answer it returns: every booking site's price for one London hotel, in one call.

curl -X GET "https://api.stayapi.com/v1/google_travel/prices?entity_token=ChUIzYGfsLP03b1HGgkvbS8wMnE4emYQAQ&currency=GBP" \
  -H "x-api-key: YOUR_API_KEY"

{
  "success": true,
  "currency": "GBP",
  "price": { "formatted": "£536", "value": 535.875 },
  "offers": [
    { "partner": "London Hilton on Park Lane", "price": "£536" },
    { "partner": "Expedia.com", "price": "£603" },
    { "partner": "Booking.com", "price": "£604" },
    ...
  ]
}

The hotel's direct rate at £536, the two largest OTAs at £603 and £604, in a payload a spreadsheet can read.
That's the rate parity picture for one property, and the same call runs for the five hotels around you.

The technical guides for this kind live elsewhere: the hotel search API guide for finding every hotel in a market, and the hotel price API guide for room-level rates.
For the review side, our hotel review sentiment analysis guide shows what revenue teams do with it.
One tradeoff, stated plainly: market data APIs return what the public sites display, so a competitor's member-only or negotiated rates aren't in the picture.

Evaluating a Hospitality API: A Non-Technical Checklist

The first three rows sort most vendor conversations in five minutes.

Getting Started

1. List the systems you run (PMS, channel manager, booking engine, guest tools) and, for each, find the API documentation page. If you can't find one, ask the vendor where it is and what it can read and write.
2. For any new integration, ask who approves it going live and what scopes it needs; that answer tells you whether it's a PMS-API connection or a services project.
3. For market data, preview the answer with the free hotel search tool before anyone writes code.
4. Sign up at stayapi.com. Free tier, no credit card, and the first call can be the one above with your own hotel's name.
5. Pipe the JSON into Google Sheets, Looker Studio, or Power BI, or wire it through no-code platforms like N8N and Make.com, so the morning rate check runs itself. For portfolio-wide market monitoring, book a demo call.

FAQ

What is an API in hotels?

An API is a documented way for one hotel system to ask another for data or send it, such as a channel manager writing rates into the PMS or a guest app reading tomorrow's arrivals.
Hospitality APIs come in five kinds: PMS, distribution, booking engine and payments, guest-facing, and market data.

What is OHIP?

OHIP is Oracle Hospitality Integration Platform, the API layer for OPERA Cloud.
Its specifications are public on GitHub, vendors build against a partner sandbox, and access to a real hotel's environment is granted by that hotel.

Do I need a developer to use a hospitality API?

For PMS, distribution, and guest-facing kinds, the vendor's developers do the integration and the hotel approves it.
For market data, the JSON can land in a spreadsheet or a no-code workflow, so an analyst can run it without engineering time.

What's the difference between a hospitality API and a hotel data API?

Hospitality API is the umbrella for all five kinds; a hotel data API is the market-data kind, reading public booking sites for rates and reviews.
StayAPI is one example of that kind, and the explainer linked in the takeaways covers it in depth.

Can a PMS API show competitor prices?

No.
A PMS API exposes the hotel's own reservations, rates, and profiles; competitor prices and reviews come from market data APIs that read the public booking sites.