canonical: https://jentic.com/apis/hotelumo.com/hotelumo

# Hotelumo API

The Hotelumo API runs hotel room reservations end to end: it finds available room offers for a stay, requests and creates reservations, approves requested ones, and keeps guest profiles, room types, rate plans, and daily rates in sync. Webhook subscriptions push reservation events to your systems as they happen. Use it to let an app or an agent check availability and book rooms directly against a property's inventory and rates.

## For AI agents

Check hotel room availability, request and create reservations, approve them, and manage guests, room types, rate plans, and daily rates for a property.

## Scope

Does not process card payments, sell flights, or publish reviews. Use for hotel availability, reservations, guests, and rate management only.

## Capabilities

- Find public room offers for a stay by hotel and dates
- Request and create room reservations
- Approve a requested reservation to confirm it
- Create and update guest profiles
- Manage room types and individual rooms
- Set rate plans and upsert daily rates for a date range
- Subscribe to webhooks for reservation events

## Use cases

### Availability and Booking

Check a property's live room offers for a stay and request the booking in one flow, rather than integrating a channel feed by hand. The API returns public room offers for a hotel and dates, then takes a reservation request against that availability. Booking tools use this to turn an availability check into a confirmed request.

Example prompt: GET `/api/hotels/{hotelId}/availability` for the stay dates, then POST `/api/hotels/{hotelId}/book-reservation` to request the room.

### Reservation Management

Create reservations and move requested ones to confirmed so a property's booking records stay accurate. The API creates a reservation and approves a requested reservation by id. Front-desk and operations tools use this to manage the reservation lifecycle programmatically.

Example prompt: POST `/api/reservations` to create a reservation, then POST `/api/reservations/{reservationId}/approve` to confirm a requested one.

### Rate and Inventory Updates

Keep room rates and inventory current by setting rate plans and upserting daily rates for a date range. The API upserts daily rates and creates or updates rate plans and room types. Revenue teams use this to push pricing changes without logging into the property dashboard.

Example prompt: POST `/api/dailyRates` to upsert rates for a date range, then POST `/api/ratePlans` to update a rate plan.

### Agent-Assisted Booking

An AI agent checks availability and books a room for a guest without a bespoke property integration. Through Jentic the agent discovers the availability, guest, and booking operations, loads their schemas, and chains them to complete a request. This lets a travel assistant book directly against a property's inventory.

Example prompt: Search Jentic for 'find hotel availability', call GET `/api/hotels/{hotelId}/availability`, create or reuse a guest with POST `/api/guests`, and book with POST `/api/hotels/{hotelId}/book-reservation.`

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/hotels/{hotelId}/availability` | Find public room offers for a stay |
| POST | `/api/hotels/{hotelId}/book-reservation` | Request a room reservation |
| GET | `/api/reservations` | List reservations |
| POST | `/api/reservations` | Create a reservation |
| GET | `/api/guests` | List guests |
| POST | `/api/guests` | Create a guest |
| GET | `/api/rooms` | List rooms |
| GET | `/api/ratePlans` | List rate plans |

## Key resources

- **Availability and Booking** — Find public room offers for a stay and request a reservation for a hotel
- **Reservations** — Create, read, update, delete, and approve reservations
- **Guests** — Create, read, update, and delete guest profiles
- **Rooms and Rates** — Manage rooms and room types and upsert rate plans and daily rates
- **Webhook Subscriptions** — Create, update, and delete webhook subscriptions for events

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 58 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 30 / 100
  - AI Discoverability: 85 / 100
- **View full report:** https://jentic.com/apis/hotelumo.com/hotelumo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Hotelumo by hand means handling either HTTP Basic or an access token, then checking availability and sequencing the guest and reservation calls yourself. Through Jentic you install once, import Hotelumo from the API Directory, store the credential once, and your agent calls those operations in order.
- **Permission scoping:** Hotelumo puts the hotel, reservation, and guest id in the URL path, such as `/api/hotels/{hotelId}/availability` and `/api/reservations/{reservationId}`, so a rule can pin your agent to one hotel. You choose the operations it may call, so write operations like deleting a reservation or a guest are not included unless you add them.
- **Credential handling:** Your Hotelumo credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find hotel availability' or 'book a room', and Jentic returns the matching Hotelumo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudbeds API** — Hotel property management and booking platform
- **apaleo API** — API-first property management system for hotels
- **Beds24 API** — Channel manager syncing availability across OTAs

## FAQ

### Is there a Hotelumo MCP server?

You do not need an MCP server to give your agent the Hotelumo API. Jentic connects it directly from the API Directory: import Hotelumo, store your credential once, and your agent calls the availability, reservation, and guest endpoints. Operations are discovered on demand, so no extra server's tool definitions load into the agent's context.

### What authentication does the Hotelumo API use?

The Hotelumo API authenticates with HTTP Basic credentials or an access token passed in the Authorization header, per its OpenAPI spec. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

### Can I check availability and book a room with the Hotelumo API?

Yes. GET `/api/hotels/{hotelId}/availability` returns public room offers for a stay, and POST `/api/hotels/{hotelId}/book-reservation` requests a room against that availability. A requested reservation is then confirmed with POST `/api/reservations/{reservationId}/approve.`

### What are the rate limits for the Hotelumo API?

The OpenAPI spec does not specify rate limits for the Hotelumo API. Check the Hotelumo documentation at https://www.hotelumo.com for the current limits that apply to your account.

### How do I find hotel availability through Jentic?

Search Jentic with the query 'find hotel availability', load the schema for GET `/api/hotels/{hotelId}/availability`, and execute it with the hotel and stay dates to get room offers. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Hotelumo API?

Yes. Write a rule that allows only the read and booking operations for one hotel, such as GET `/api/hotels/{hotelId}/availability` and POST `/api/hotels/{hotelId}/book-reservation`, so the agent can check rooms and request bookings but cannot delete reservations or change rate plans, and every call it makes is logged. Because the hotel and reservation ids live in the URL path, you can pin it to a single property.