canonical: https://jentic.com/apis/hetras-certification.net/hetras-hotel-api-version-0

# Hetras Certification hetras Hotel API Version 0

The hetras Hotel API exposes hotel-side configuration on the hetras hotel management platform, used by hotel chains to expose property setup data to integrations. It covers the hotels accessible to the calling application, the codes catalogue, rate plans and their daily rates, room types, and individual rooms. This is the right surface for tools that read or update underlying hotel configuration rather than guest-facing reservations.

## For AI agents

Read and update hotel-side configuration on hetras - hotels, codes, rate plans, daily rates, room types, and rooms.

## Scope

Does not create or modify guest reservations and does not run check-in or check-out - use the hetras Booking API for those, and this Hotel API for hotel, code, rate plan, room type, and room configuration only.

## Capabilities

- List the hotels of a chain that the application has access to
- Get details for a specific hotel by ID
- Look up codes (categories, channels, segments) for a hotel
- List and inspect rate plans defined on a hotel
- Update base rate plan rates for a period in a single batch call
- Read and partially update daily rates for a rate plan and date range
- List room types and individual rooms configured for a hotel

## Use cases

### Revenue Management Rate Push

Revenue management systems running their own pricing models can push updated daily rates back to hetras through the rate plan rates endpoints. The batch endpoint accepts a base price for a list of rate plans across a defined period, so a nightly job can push the next horizon in a single call. This keeps hetras as the system of record while letting external pricing tools own the math.

Example prompt: PUT `/api/hotel/v0/hotels/{hotelId}/rateplans/batch`/$rates with the rate plan list, period, and base prices.

### Property Configuration Replication

Integrations that replicate hetras property setup into a data warehouse can pull hotels, codes, rate plans, and room types on a schedule. The endpoints support scoped reads per hotel, so the replication job can iterate the chain's hotels without pulling unrelated data. Downstream BI tools then have a clean copy of the configuration tables for analysis.

Example prompt: GET `/api/hotel/v0/hotels`, then for each hotel GET /rateplans, /room_types, and /codes and load the results into the warehouse.

### Channel Manager Rate Plan Discovery

When a hotel onboards a new OTA, the channel manager needs to discover the available rate plans and room types so it can map them to the OTA's product taxonomy. The Hotel API's rate plan and room type endpoints provide this configuration in JSON, removing the need to scrape the hetras admin UI. Mappings can then be confirmed once and reused.

Example prompt: GET `/api/hotel/v0/hotels/{hotelId}/rateplans` and GET `/api/hotel/v0/hotels/{hotelId}/room_types` and present them for mapping in the channel manager UI.

### AI Agent Configuration Auditor

An AI agent acting as a hotel ops auditor can use Jentic to walk a chain's hetras configuration and flag inconsistencies - missing rate plans, room types without rooms, codes that no longer match the tagging convention. The credentials sit in your Jentic One instance and the agent works from declared schemas, so audits are repeatable and side-effect free when the agent stays on the GET endpoints. This is well suited to chains running many hetras-managed properties.

Example prompt: Search Jentic for 'list hetras hotels', load GET `/api/hotel/v0/hotels`, and execute, then walk each hotel's rate plans and room types.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/hotel/v0/hotels` | List hotels accessible to the application |
| GET | `/api/hotel/v0/hotels/{hotelId}` | Get details for a specific hotel |
| GET | `/api/hotel/v0/hotels/{hotelId}/codes` | List codes for a hotel |
| GET | `/api/hotel/v0/hotels/{hotelId}/rateplans` | List rate plans for a hotel |
| PUT | `/api/hotel/v0/hotels/{hotelId}/rateplans/batch/$rates` | Bulk update base rate plan rates |
| GET | `/api/hotel/v0/hotels/{hotelId}/rateplans/{rateplanCode}/rates` | Get daily rates for a rate plan |
| PATCH | `/api/hotel/v0/hotels/{hotelId}/rateplans/{rateplanCode}/rates` | Partially update daily rates for a rate plan |
| GET | `/api/hotel/v0/hotels/{hotelId}/room_types` | List room types configured for a hotel |

## Key resources

- **Hotels** — Hotels accessible to the application and their details
- **Codes** — Codes catalogue for a hotel filtered by type or code
- **RatePlans** — Rate plans defined on a hotel
- **Daily Rates** — Daily rates for a rate plan and date range, partially updatable
- **RoomTypes** — Room types configured for a hotel
- **Rooms** — Individual rooms within a hotel

## Why Jentic

- **Setup:** Wiring the hetras Hotel API by hand means handling the partner credentials the platform issues and writing your own retry logic across hotel, code, rate plan, and room type configuration. Through Jentic you install once, import the hetras Hotel API from the API Directory, store the partner credential once, and your agent calls it.
- **Permission scoping:** The Hotel API puts the hotel and rate plan id in the URL path (`/hotels/{hotelId}/rateplans/{rateplanCode}`), so a rule can pin your agent to configuring one hotel. You choose the operations it may call, so updating rates with PUT or PATCH is only included if you add it, while reading hotels, codes, and rate plans stays separate.
- **Credential handling:** Your hetras partner 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 'list hetras rate plans' or 'read room types for a hotel', and Jentic returns the matching Hotel API operation with its input schema including the code and rate plan filter parameters, so the agent calls the right endpoint without reading the certification documentation.

## Related APIs

- **hetras Booking API Version 0** — Guest-facing booking and reservation lifecycle counterpart
- **Cloudbeds API** — Cloud property management system with config and booking in one API
- **Amadeus Hotel Search API** — Hotel inventory search across global travel distribution

## FAQ

### What authentication does the hetras Hotel API use?

The certification spec exposes the API surface without a defined security scheme - production access requires a partner-issued credential negotiated with hetras. When called through Jentic, that credential is stored in your Jentic One instance and supplied to each request at execution time.

### Can I update rate plan rates in bulk?

Yes. PUT `/api/hotel/v0/hotels/{hotelId}/rateplans/batch`/$rates accepts a list of rate plans, a period, and a base price for single occupancy, applying the change in one call. Use this for nightly horizon pushes from a revenue management system.

### How do I list all hotels my application can access?

GET `/api/hotel/v0/hotels` returns the chain's hotels visible to the calling application. Iterate the result and call GET `/api/hotel/v0/hotels/{hotelId}` for each one to retrieve the full hotel record.

### What are the rate limits for the hetras Hotel API?

Rate limits are not published in the certification spec and are governed by the partner contract with hetras. Schedule large configuration syncs with the hetras team rather than running them ad hoc against the certification environment.

### How do I retrieve daily rates through Jentic?

Search Jentic for 'get hetras daily rates', load GET `/api/hotel/v0/hotels/{hotelId}/rateplans/{rateplanCode}/rates`, and execute with the rate plan code and a date range. Jentic injects the partner credential from the vault.

### Can the API list room types and rooms?

Yes. GET `/api/hotel/v0/hotels/{hotelId}/room_types` lists all configured room types, and per-room endpoints expose individual room records. Use these together when mapping hetras inventory to a channel manager or PMS.

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

Yes. Because you run Jentic One yourself, your own rules decide which hetras Hotel API operations and credentials the agent may use. Since the hotel and rate plan IDs sit in the URL path, such as `/hotels/{hotelId}/rateplans/{rateplanCode}`, you can pin the agent to a single hotel, and you keep read-only calls like GET /hotels, /codes, and /rateplans separate from write calls. Rate updates through PUT `/rateplans/batch`/$rates or PATCH on daily rates are only available to the agent if you add them.