hetras APIs for AI Agents
E CommerceInventoryOrder ManagementThird-Party SpecsNo authAgent Ready
hetras API Catalog
2 APIs across 1 product group. All share one credential.
E Commerce2
hetras Hotel API Version 0Read and update hotel-side configuration on hetras - hotels, codes, rate plans, daily rates, room types, and rooms.~21 endpointshetras Booking API Version 0Look up hotel availability, fetch rates and addons, create bookings, assign rooms, and run check-in or check-out on the hetras hotel platform.~19 endpoints
Which hetras API should I use?
| I want to... | Use | 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. |
Install Jentic One Beta
Connect the hetras APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the hetras APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhetras-certification.net" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhetras-certification.net" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: .
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
FAQs
Specific to using hetras APIs through Jentic.
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.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
