hetras Booking API Version 0

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

★ Only Publicly Available OpenAPI DocumentE CommerceOrder Managementnone19 EndpointsREST

For Agents

Look up hotel availability, fetch rates and addons, create bookings, assign rooms, and run check-in or check-out on the hetras hotel platform.

Quickstart

Get started with hetras Booking 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:
"create a hotel booking"

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

Capabilities

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

Look up room availability and occupancy for a property and date range

Retrieve daily rates and rate plans for the booking engine

List blocked inventory holds via the blocks endpoints

Offer addon services for a specific guest stay through the addons endpoint

GET STARTED

Start building with hetras Booking API Version 0 API

Explore with Jentic

View OpenAPI Document

Use for: I need to check room availability for a hotel between two dates, I want to create a new hotel booking with two reservations, Find a reservation by its confirmation ID, Get all addons offered for a specific guest stay

Not supported: Does not configure hotels, rate plans, or room types — use the hetras Hotel API for those, and this Booking API for availability, rates, addons, and the reservation lifecycle only.

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

The hetras Booking API exposes the booking-side surface of the hetras hotel management platform, used by hotel chains running on the hetras cloud. It covers room availability and occupancy lookups, block and rate retrieval, addon offers for guest stays, and the full reservation lifecycle including create, partial update, room assignment, check-in, check-out, and cancellation. This is the integration point for booking engines, channel managers, and front-desk tools that need to reserve and manage stays on hetras-managed properties.

Use Cases

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

★ Direct Booking Engine Integration

Hotel websites running their own booking engine can call the hetras Booking API to check availability, present rates and addons, and create the reservation when the guest confirms. The API returns confirmation IDs that the website can show on the success page and email back to the guest. This avoids reselling inventory through an OTA when the customer has come to the hotel directly.

GET /api/booking/v0/availability for the dates, then POST /api/booking/v0/bookings with the chosen rate and guest payload.

Channel Manager Sync

Channel managers that distribute hotel inventory to OTAs and metasearch sites can pull availability and rate data on a tight schedule and push reservations back when an OTA confirms a booking. The hetras Booking API provides the symmetric pull and push surface, so the channel manager can keep all distribution channels in sync. Rates and blocks fetched here become the source of truth for outbound feeds.

GET /api/booking/v0/availability and GET /api/booking/v0/dailyrates on a schedule and feed each OTA the merged result.

Front-Desk Check-in and Check-out

Front-desk staff using a custom property management UI can drive the check-in and check-out flow through the reservation sub-resources. Assigning a room, performing check-in, then later check-out, all map cleanly to dedicated endpoints. This keeps the front desk in their preferred UI without losing the platform's lifecycle guarantees.

POST /api/booking/v0/bookings/{confirmationId}/reservations/{reservationNumber}/assign_room, then /check_in on arrival and /check_out on departure.

AI Agent Booking Assistant

An AI travel assistant connected through Jentic can search hetras-managed hotels for availability, present rates, and create a reservation on behalf of the user once a choice is made. Jentic isolates the API access and exposes only the operations the agent needs, so the assistant cannot invent or misuse endpoints. This pattern fits travel concierge agents that own end-to-end booking inside a controlled hotel portfolio.

Search Jentic for 'create a hotel booking', load POST /api/booking/v0/bookings, and execute with the chosen hotel, dates, rate, and guest details.

Key Endpoints

19 endpoints — the hetras booking api exposes the booking-side surface of the hetras hotel management platform, used by hotel chains running on the hetras cloud.

METHOD

PATH

DESCRIPTION

GET

/api/booking/v0/availability

Get availability and occupancy for a hotel and timespan

GET

/api/booking/v0/bookings

Find bookings matching filter criteria

POST

/api/booking/v0/bookings

Create a new booking

GET

/api/booking/v0/bookings/{confirmationId}

Load all reservations for a booking

PATCH

/api/booking/v0/bookings/{confirmationId}/reservations/{reservationNumber}

Partially update a reservation

POST

/api/booking/v0/bookings/{confirmationId}/reservations/{reservationNumber}/check_in

Check in a reservation

POST

/api/booking/v0/bookings/{confirmationId}/reservations/{reservationNumber}/check_out

Check out a reservation

POST

/api/booking/v0/bookings/{confirmationId}/reservations/{reservationNumber}/cancel

Cancel a reservation

GET

/api/booking/v0/availability

Get availability and occupancy for a hotel and timespan

GET

/api/booking/v0/bookings

Find bookings matching filter criteria

POST

/api/booking/v0/bookings

Create a new booking

GET

/api/booking/v0/bookings/{confirmationId}

Load all reservations for a booking

PATCH

/api/booking/v0/bookings/{confirmationId}/reservations/{reservationNumber}

Partially update a reservation

Why though Jentic?

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

Credential isolation

Partner credentials for the hetras platform are stored in the Jentic vault. Jentic adds the negotiated credential to each request, so the agent never sees the raw secret.

Intent-based discovery

Agents search by intent (e.g., 'create a hotel booking') and Jentic returns the matching hetras Booking operation with its input schema, so the agent does not need to read the certification documentation.

Time to first call

Direct hetras integration: 1-2 weeks once partner credentials are issued, given the booking and reservation lifecycle. Through Jentic: under an hour to make the first availability or booking call once credentials are loaded.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

hetras Hotel API Version 0

Hotel-side configuration: hotels, rate plans, room types, codes

Use the Booking API for guest reservations and the Hotel API for the underlying hotel, rate plan, and room type setup.

Alternative

Cloudbeds API

Cloud property management system for independent hotels

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

Alternative

Amadeus Hotel Booking API

Global travel distribution hotel booking API

Pick Amadeus when booking across many global chains via a GDS-style aggregator; pick hetras Booking when working directly with a hetras-managed property portfolio.

FAQs

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

What authentication does the hetras Booking API use?

The certification spec exposes the API surface without a defined security scheme — the production hetras platform requires a partner-issued credential negotiated with hetras directly. When called through Jentic, that credential is held in the Jentic vault and supplied at execution time once configured by the operator.

Can I check hotel availability and occupancy through the API?

Yes. GET /api/booking/v0/availability returns availability and occupancy for a specific hotel and date range. Use the response together with GET /api/booking/v0/dailyrates to price a stay before creating a booking.

How do I create a booking and assign a room on arrival?

POST /api/booking/v0/bookings creates the booking with one or more reservations. On arrival, POST /api/booking/v0/bookings/{confirmationId}/reservations/{reservationNumber}/assign_room sets the physical room, then /check_in performs the front-desk check-in step.

What are the rate limits for the hetras Booking API?

Rate limits are not published in the certification spec and are governed by the partner contract with hetras. Treat the certification environment as low-volume — heavy use should be scheduled with the hetras team to avoid throttling.

How do I cancel a reservation through Jentic?

Search Jentic for 'cancel a hetras reservation', load POST /api/booking/v0/bookings/{confirmationId}/reservations/{reservationNumber}/cancel, and execute with the confirmation ID and reservation number. Inventory is returned to the pool on success.

Can the API offer addons during the booking flow?

Yes. GET /api/booking/v0/addons returns the addons available for a specific guest stay (room type, dates, occupancy). Surface those offers in the booking UI before the guest confirms so addon revenue is captured at the point of sale.