hetras Hotel API Version 0

Name: hetras Hotel API Version 0 API
Brand: hetras Hotel API Version 0
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceInventorynone21 EndpointsREST

For Agents

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

Quickstart

Get started with hetras Hotel API Version 0 in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list hetras hotels and rate plans"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with hetras Hotel API Version 0 API.

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

GET STARTED

Start building with hetras Hotel API Version 0 API

Explore with Jentic

View OpenAPI Document

Use for: I need to list all hotels my application can access, I want to update daily rates for a rate plan over the next 30 days, Get the details of a specific hotel by ID, Retrieve all codes of a given type for a hotel

Not supported: 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.

Jentic publishes the only available OpenAPI document for hetras Hotel API Version 0, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use hetras Hotel API Version 0 API for, with concrete tasks.

★ 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.

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.

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.

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 the Jentic vault 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.

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

21 endpoints — 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.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Partner credentials issued by hetras are stored in the Jentic vault. Jentic supplies them on every Hotel API call, so the agent never holds the secret in its context.

Intent-based discovery

Agents search by intent (e.g., 'list hetras rate plans') and Jentic returns the matching Hotel API operation with its input schema, including filter parameters for codes and rate plans.

Time to first call

Direct hetras Hotel API integration: 1-2 weeks to model rate plans, room types, and codes against the consuming system. Through Jentic: under an hour to make the first configuration read once credentials are loaded.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

hetras Booking API Version 0

Guest-facing booking and reservation lifecycle counterpart

Use the Hotel API for property configuration and the Booking API when the agent needs to take or modify reservations.

Alternative

Cloudbeds API

Cloud property management system with config and booking in one API

Choose Cloudbeds when the property is on Cloudbeds; choose hetras Hotel when the property is on the hetras platform.

Alternative

Amadeus Hotel Search API

Hotel inventory search across global travel distribution

Pick Amadeus Hotel Search for global multi-chain discovery; pick hetras Hotel when working with a specific chain's hetras-managed configuration.

FAQs

Specific to using hetras Hotel API Version 0 API through Jentic.

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 the Jentic vault 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.