Install Jentic One Beta

Connect the Newbook OTA API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Newbook OTA API, 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.

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%2Fnewbook.cloud%2Fnewbook" | sh

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%2Fnewbook.cloud%2Fnewbook" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Newbook OTA API.

Test connectivity and credentials with the OTA Ping message

Retrieve descriptive hotel and instance information for connected properties

Get the room types and rate plan mapping for a property to drive a booking surface

Check live availability and rates for a property across given dates and occupancies

Read existing booking details by reservation reference

GET STARTED

Start building with Newbook OTA API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Newbook OTA API for, with concrete tasks.

★ OTA Channel Booking Push

Online travel agencies that take a reservation on their own surface forward the booking into Newbook by calling POST /OTA_HotelResNotifRQ with the OTA-formatted booking message. Newbook records the reservation against the property and the property staff see the new booking in their PMS without any manual entry.

POST to /OTA_HotelResNotifRQ with the OTA HotelResNotif message containing the guest, property, room type, rate plan, and arrival/departure dates; record Newbook's confirmation reference in the OTA's order record.

Real-Time Availability and Rate Lookup

Booking surfaces and metasearch integrations call POST /OTA_HotelAvailRQ to fetch live availability and pricing for a property and date range before quoting a guest. The response feeds the displayed rate so the guest only sees offers Newbook can actually fulfil.

POST to /OTA_HotelAvailRQ with the property code, arrival and departure dates, and occupancy; surface the cheapest available rate plan in the booking widget.

Reservation Modification and Cancellation

Guest service teams modify or cancel an existing booking by sending a HotelResNotif message with status 'Modify' or 'Cancel' through POST /OTA_HotelResNotifRQ. Newbook applies the change to the property's PMS calendar and inventory immediately, eliminating the dual-entry problem when handling changes from multiple channels.

POST to /OTA_HotelResNotifRQ with the existing reservation reference and a HotelResNotif message in 'Cancel' status to release the inventory back to availability.

AI Agent Concierge for Properties

A property concierge agent uses Jentic to discover Newbook OTA operations and answers guest questions like 'is a king room available next Friday?' by calling /OTA_HotelAvailRQ behind the scenes, then proceeds to /OTA_HotelResNotifRQ once the guest confirms - all through one credential bound at the agent level.

Use Jentic to search 'check hotel availability', load POST /OTA_HotelAvailRQ, execute it for the guest's dates, and on confirmation call POST /OTA_HotelResNotifRQ to create the booking.

Key Endpoints

7 endpoints — the newbook ota api exposes newbook's property management system over open travel alliance (ota) message contracts, represented here as rest endpoints that wrap soap/xml payloads.

METHOD

PATH

DESCRIPTION

POST

/OTA_PingRQ

Connection test

POST

/OTA_HotelDescriptiveInfoRQ

Retrieve hotel and instance information

POST

/GetMappingRQ

Get room types and rate plans

POST

/OTA_HotelAvailRQ

Check availability and rates

POST

/OTA_ReadRQ

Retrieve booking details

POST

/OTA_HotelResNotifRQ

Create, modify, or cancel bookings

POST

/ARISettingsRQ

Configure ARI push settings

POST

/OTA_PingRQ

Connection test

POST

/OTA_HotelDescriptiveInfoRQ

Retrieve hotel and instance information

POST

/GetMappingRQ

Get room types and rate plans

POST

/OTA_HotelAvailRQ

Check availability and rates

POST

/OTA_ReadRQ

Retrieve booking details

POST

/OTA_HotelResNotifRQ

Create, modify, or cancel bookings

POST

/ARISettingsRQ

Configure ARI push settings

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Newbook OTA API by hand means building its WSSE header, targeting the apius.newbook.cloud/ota host, and shaping the OTA request messages for availability, rates, and reservations yourself. Through Jentic you install once, import Newbook OTA from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Newbook takes its property and reservation details inside the OTA request body, so limit the agent to the operations it needs, such as checking availability or reading a reservation, and leave out the ones it should not run, such as posting a reservation notification.

Credential isolation

Your Newbook WSSE credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check hotel availability' or 'create a hotel booking', and Jentic returns the matching Newbook OTA operation with its input schema so the agent calls the right endpoint without browsing the OTA schemas by hand.

FAQs

Specific to using Newbook OTA API through Jentic.

What authentication does the Newbook OTA API use?

Newbook OTA uses a WSSE header passed on every request. Through Jentic, the WSSE credential is stored in the encrypted Jentic One instance and injected at request time so it never appears in the agent's context.

Can I create bookings through the Newbook OTA API?

Yes. POST /OTA_HotelResNotifRQ accepts an OTA HotelResNotif message in 'Commit', 'Modify', or 'Cancel' status to create, change, or cancel a reservation in Newbook. The endpoint returns Newbook's confirmation reference for use in your own order record.

How do I check live availability and rates through Jentic?

Search Jentic for 'check hotel availability', load POST /OTA_HotelAvailRQ, and execute it with the property code, dates, and occupancy. The response contains the bookable rate plans and prices that Newbook will honour.

What are the rate limits for the Newbook OTA API?

Rate limits are not published numerically in the spec - Newbook scales API capacity by the property and channel partner agreement. Coordinate concurrency expectations with Newbook before running heavy availability polling against many properties.

Is the Newbook OTA API REST or SOAP?

The underlying contract is OTA SOAP/XML. Newbook represents each OTA message as a REST endpoint that accepts the corresponding XML body, so HTTP clients can call /OTA_HotelResNotifRQ etc. without a SOAP toolkit.

Is the Newbook OTA API free?

API access is included with Newbook's PMS subscription for connected properties or channel partners. There is no separate API tier - credentials are issued by Newbook as part of the partner onboarding process.

Can I limit what my agent is allowed to do with the Newbook OTA API?

Yes. Because Jentic One is self-hosted, your own rules decide which Newbook OTA operations and credentials the agent may use. You can allow read-only calls such as checking availability and rates with /OTA_HotelAvailRQ or reading a reservation with /OTA_ReadRQ, while leaving out write operations like creating, modifying, or cancelling a booking through /OTA_HotelResNotifRQ. The WSSE credential is injected only for the operations you permit, so the agent cannot call anything you have not scoped.

Newbook OTA API

Name: Newbook OTA API
Brand: Newbook OTA API
Availability: InStock

Official vendor OpenAPI document · agent-readyE CommerceOrder ManagementapiKey7 EndpointsREST

For Agents

Read accommodation availability and rates and create, modify, or cancel bookings against Newbook properties through OTA-style messages.

Use for: Check availability and rates for a property next week, Create a booking at a Newbook property for two guests, Modify an existing reservation's check-out date, Cancel a Newbook booking by reservation reference

Not supported: Does not handle payments, guest communications, or housekeeping operations - use for OTA-style availability, rates, and reservation messages against Newbook properties only.

The Newbook OTA API exposes Newbook's property management system over Open Travel Alliance (OTA) message contracts, represented here as REST endpoints that wrap SOAP/XML payloads. Channel managers, OTAs, and direct booking surfaces use it to read availability and rates, push reservations, modify or cancel bookings, and manage availability and rate inventory (ARI) for accommodation properties. Authentication uses a WSSE header passed on every request.

Jentic One on Github View OpenAPI Document

Connect the Newbook OTA API to your agent

Capabilities

Start building with Newbook OTA API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Newbook OTA API