A new index scores 343 PMS vendors on API access. Only 7% publish open docs

A new index has scored property management systems on how open their APIs actually are, and the headline number is unflattering. Of 343 PMS vendors audited, 24 publish fully self-serve API documentation. That is 7%. The other 93% keep their APIs gated, undocumented, or both.

The 2026 PMS API Power Index comes from the AI Hospitality Alliance, working with HotelLogic. It scores vendors across ten capability dimensions on a 0 to 100 scale, covering documentation, integration readiness, webhook maturity and what the authors call AI readiness.

Eighteen vendors were scored in full detail. Those composite scores run from 80.0 at the top to 26.3 at the bottom, and thirteen of the eighteen came in below 60.

Mews scored highest at 80.0. Apaleo, Oracle OPERA Cloud, Beds24 and Cloudbeds made up the rest of the top five, all at 73.3 or above. The lowest score, 26.3, went to Oracle OPERA 5.

One finding cuts against the rest of the report. On governance and security, only two of the eighteen profiles scored above 3. Ira Vouk, founder of the AI Hospitality Alliance, is listed as the contact for the research.

What it means for operators

Start with the gap inside Oracle, because it is the most actionable thing here. OPERA Cloud sits in the top five and OPERA 5 sits last. That is not two vendors. It is one vendor's cloud product and its older on-premise product, and the spread between them is a fair proxy for how much integration pain a property still running OPERA 5 should expect. If you are on it and have been told a migration can wait, this is a number to put in front of whoever decides.

Second, treat the 7% figure as a purchasing prompt rather than a scandal. Plenty of vendors gate API documentation behind a partner agreement for ordinary commercial reasons. The problem is what that does to you at signing time, when you cannot check whether the system will talk to your locks, your revenue tool or your accounting package until after you have committed. Ask for the API documentation during the sales process. A vendor who will not show it before contract is telling you something.

Third, the governance result deserves more attention than it is likely to get. A well documented, wide open API combined with weak governance controls is not obviously safer than a closed one, because the things reading your guest data are now easier to connect and no better supervised. Sixteen of eighteen scoring at or below 3 on that dimension is the finding to raise with your own vendor.

Two caveats on the study itself. Eighteen full profiles out of 343 audited vendors is a thin base for a league table, and the omissions will matter to anyone whose system is not in it. And the index is published by a body whose stated purpose is advancing AI adoption in hospitality, which makes it an argument for open APIs before it is a neutral measurement of them.

The 7% headline is still a useful number. The ranking underneath it is a starting point for questions, not a verdict.