canonical: https://jentic.com/apis/hetras-certification.net

# hetras APIs

hetras is a cloud hotel management platform for hotel chains. Its APIs split cleanly into two surfaces: the Hotel API for property-side configuration such as hotels, codes, rate plans, daily rates, room types, and rooms, and the Booking API for the guest reservation lifecycle including availability lookups, rates, addons, booking creation, room assignment, check-in, check-out, and cancellation. Together they let integrations read and update hotel setup and take or modify reservations against hetras-managed properties.

## For AI agents

An agent can read and update hotel configuration on hetras such as rate plans, daily rates, room types, and rooms, then check availability, create bookings, and run room assignment, check-in, check-out, and cancellation against those same properties.

## Scope

Use for: Reading and updating hetras hotel configuration and running the guest booking lifecycle against properties on the hetras cloud platform

Not supported:
- cross-chain distribution
- guest payment processing
- channel manager hosting
- OTA connectivity
- published rate limits

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| hetras Hotel API Version 0 | e-commerce | 21 | Read and update hotel-side configuration on hetras - hotels, codes, rate plans, daily rates, room types, and rooms. |
| hetras Booking API Version 0 | e-commerce | 19 | Look up hotel availability, fetch rates and addons, create bookings, assign rooms, and run check-in or check-out on the hetras hotel platform. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Set up or read hotels, codes, rate plans, daily rates, room types, and rooms | hetras-hotel-api-version-0 | The Hotel API owns property-side configuration and does not touch guest reservations. |
| Check availability, create bookings, assign rooms, or run check-in and check-out | hetras-booking-api-version-0 | The Booking API owns the reservation lifecycle and reads the rate plans the Hotel API configures. |
| Push updated daily rates from a revenue management system | hetras-hotel-api-version-0 | Rate plan rate updates live on the Hotel API, including the batch rates endpoint. |

## Cross-API use cases

### Configure a hotel then take bookings

An integration reads a hotel's rate plans and room types from the Hotel API to build its booking screen, then checks availability and creates reservations through the Booking API against the same property. The configuration read and the reservation write share one partner credential.

Example prompt: GET /api/hotel/v0/hotels/{hotelId}/rateplans to load the rate plans, then GET /api/booking/v0/availability and POST /api/booking/v0/bookings to create the reservation.

### Channel manager sync across config and inventory

A channel manager discovers rate plans and room types from the Hotel API to map them to an OTA product taxonomy, then pulls availability and daily rates from the Booking API on a schedule and pushes confirmed reservations back. Both feeds run through the same hetras platform access.

Example prompt: GET /api/hotel/v0/hotels/{hotelId}/room_types to map products, then poll GET /api/booking/v0/availability and POST /api/booking/v0/bookings on OTA confirmations.

### Revenue management price and occupancy loop

A revenue tool reads occupancy from the Booking API availability endpoint, computes new prices, and pushes them back to the Hotel API rate plan rates in a batch call so the next horizon reflects demand. hetras stays the system of record while the external model owns the math.

Example prompt: GET /api/booking/v0/availability for occupancy, then PUT /api/hotel/v0/hotels/{hotelId}/rateplans/batch/$rates with the new base prices.

## Why Jentic

- **Setup:** Wiring both hetras APIs by hand means handling the partner credential the platform negotiates and writing retry logic across configuration reads and the reservation lifecycle. Through Jentic you install Jentic One once, add the hetras Hotel and Booking APIs from the Jentic directory, store the partner credential once, and your agent calls both.
- **Permission scoping:** hetras puts the hotel, rate plan, and reservation identifiers in the URL path, so your own rules can pin an agent to one hotel or one booking. You choose which operations the agent may call, so writing rates or running check-in, check-out, and cancel is included only if you add it, while reading configuration and availability 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, and the same stored credential serves both the Hotel and Booking APIs.
- **Discovery method:** An agent searches the Jentic directory by intent such as 'list hetras rate plans' or 'create a hotel booking', and Jentic returns the matching hetras operation with its input schema, so the agent picks the right endpoint across both APIs without reading the certification documentation.

## Related vendors

- **Cloudbeds** — Cloud property management system that combines configuration and booking in one API; an alternative when a property runs on Cloudbeds rather than hetras.
- **Amadeus** — Global travel distribution provider with hotel search and booking APIs; suited to cross-chain discovery where hetras targets a single managed portfolio.
- **Mews** — Cloud hospitality platform with property configuration and reservation APIs; a comparable hotel management stack for chains not on hetras.

## FAQ

### What can an agent do across the hetras APIs?

An agent can read and update hotel-side configuration through the Hotel API, including hotels, codes, rate plans, daily rates, room types, and rooms, and it can run the full guest reservation lifecycle through the Booking API, including availability lookups, rate and addon retrieval, booking creation, room assignment, check-in, check-out, and cancellation.

### How do the Hotel API and Booking API fit together?

The Hotel API defines the property setup that the Booking API operates against. You configure rate plans and room types on the Hotel API, then the Booking API reads that configuration to price stays, check availability, and create reservations. Keeping them separate lets you grant configuration access and reservation access independently.

### Does one credential cover both hetras APIs?

Yes. Both APIs run on the same hetras cloud platform and use a single partner-issued credential negotiated with hetras. The certification specs themselves declare no security scheme, so production access is what requires that credential.

### Which API should I start with?

Start with the Hotel API when you need to read or change property configuration such as rate plans, room types, and daily rates. Start with the Booking API when you need to check availability or take, modify, and cancel guest reservations. Many integrations use both.

### Is hetras suited to cross-chain hotel distribution?

No. hetras targets a specific portfolio of properties running on its cloud platform rather than aggregating inventory across many chains. For global multi-chain discovery you would use a distribution aggregator, and for a single hetras-managed portfolio you would use these APIs directly.

### Are these the production or certification endpoints?

The specs in the directory are the hetras certification versions. They describe the same API surface as production but do not publish rate limits or a security scheme, both of which are governed by your partner contract with hetras. Schedule heavy configuration or booking loads with the hetras team.