ibelsa.rooms · PMS Power Index
Composite score: 58.0 / 100 (published snapshot v2026.1, 2026-07-06)
ibelsa.rooms scores 58.0 out of 100 on the PMS Power Index. Evidence-backed diagnostic across ten API capabilities. Vendor-neutral. Open to dispute.
Scores by capability
Marketplace coverage
Score: 6 of 9 (Adequate). Weight 10%.
First scorer rationale: 6+ non-channel-manager categories confirmed: POS (3POS, Hypersoft, GastroSoft), accounting, access control/door locking (Salto), revenue management (RoomPriceGenie, ParityRate), marketing/social (Zapier, Facebook, Twitter). Channel manager excluded per the roommaster ruling.
- Six-plus non-channel-manager categories confirmed: POS (3POS, Hypersoft, GastroSoft), accounting, access control (Salto), revenue management (RoomPriceGenie, ParityRate), marketing (Zapier, Facebook, Twitter). https://www.ibelsa.com/en/connections/
What you can control via the API
Score: 9 of 9 (Best-in-class). Weight 14%.
First scorer rationale: Full CRUD confirmed: reservations (create/cancel/check-in/checkout), room status, contacts, products, invoices, CashMaster invoicing, key-card linking. Covers folio, housekeeping, and reservations — clears the compound anchor_9.
- Full CRUD across reservations, room status, contacts, products, invoices, CashMaster invoicing, and key-card linking. https://rooms.ibelsa.com/api/doc
Real-time updates and webhooks
Score: 9 of 9 (Best-in-class). Weight 13%.
First scorer rationale: Self-service webhook management via API (Add/List/Update/Remove endpoints), not support-configured. Multiple event types (reservation create/cancel, contact changes, room status). Per-webhook basic auth.
- Self-service webhook management API (add/list/update/remove) with multiple event types and per-webhook basic auth. https://rooms.ibelsa.com/doc/api/webhooks
Readiness for AI agents
Score: 3 of 9 (Limited). Weight 12%.
First scorer rationale: REST + JSON only, hand-written documentation, no OpenAPI/Swagger spec, no GraphQL, no agent-specific surface.
- REST + JSON only; hand-written docs; no OpenAPI/Swagger spec, no GraphQL, no agent-specific surface. https://rooms.ibelsa.com/api/doc
Data model and multi-property design
Score: 3 of 9 (Limited). Weight 10%.
First scorer rationale: Centralised guest profile and reservation hierarchy confirmed. Multi-property support claimed only on a third-party review aggregator, not in ibelsa's own documentation — not readily available from primary source, scores per absence.
- Centralised guest profile and reservation hierarchy confirmed in primary docs; multi-property claims not confirmed in first-party sources. https://rooms.ibelsa.com/api/doc
Developer tooling and sandbox
Score: 6 of 9 (Adequate). Weight 10%.
First scorer rationale: API key creation is self-service via the "my Hotel" area, no gating or support approval required — unlike NewBook/eZee's gated sandboxes. Active documentation platform with curl examples. No official SDK found.
- Self-service API key creation via the "my Hotel" area, no gating or support approval. Active docs platform with curl examples. No official SDK found. https://rooms.ibelsa.com/api/doc
Uptime and operational discipline
Score: 3 of 9 (Limited). Weight 9%.
First scorer rationale: ibelsa-status.com is live (Instatus-hosted), with real incident history and detail pages. No published SLA percentage.
- Public status page (ibelsa-status.com, Instatus-hosted) with real incident history and detail pages. No published SLA percentage. https://ibelsa-status.com/en
Security, authentication, and compliance
Score: 3 of 9 (Limited). Weight 8%.
First scorer rationale: Hotel-specific API key plus optional partner system key; per-webhook basic auth. No OAuth2 flow.
- Hotel-specific API key plus optional partner system key; per-webhook basic auth. No OAuth2 flow. https://rooms.ibelsa.com/api/doc
Partner programme and references
Score: 3 of 9 (Limited). Weight 7%.
First scorer rationale: Integration partnerships exist and are listed, but no self-serve partner programme, published tiers, forum, or certified-partner directory found.
- Integration partnerships listed publicly; no self-serve partner programme, published tiers, forum, or certified-partner directory found. https://www.ibelsa.com/en/connections/
Documentation and changelog discipline
Score: 3 of 9 (Limited). Weight 7%.
First scorer rationale: Comprehensive and structured documentation confirmed, but most recent changelog entry is dated 20 March 2024 — approximately 21 months stale against today. Not actively maintained within a recent window, capping below the top anchor despite otherwise complete coverage.
- Structured, comprehensive docs; changelog most recently dated 20 March 2024 (~21 months stale as of publish). https://rooms.ibelsa.com/doc/api/changelog
Scores are published only where documented evidence exists. Corrections and disputes are recorded in the public changelog. The scoring rubric is published in full in the methodology.
This provider is listed in the HotelLogic marketplace →
Rank 6 of 17 scored vendors on the PMS Power Index ladder.