canonical: https://jentic.com/apis/swaggerhub.bookingexpertapi/be-connect-api

# Bookingexpertapi BE-Connect-API

API for PMS Interfaces. The API exposes 9 endpoints secured with basic authentication.

## For AI agents

Programmatically this service responses with the mapping of rooms and rates for a specified hotel, used to set rooms and rates availabilities. Covers 9 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- this service responses with the mapping of rooms and rates for a specified hotel
- used to set rooms and rates availabilities
- Integrate BE-Connect-API into automated workflows
- Query and filter BE-Connect-API records by parameters
- Monitor BE-Connect-API operational status and events

## Use cases

### Developer Tools Operations

Use the BE-Connect-API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including this service responses with the mapping of rooms and rates for a specified hotel, used to set rooms and rates availabilities, used to set rooms and rates restrictions.

Example prompt: Call GET `/inventory/{hotel}` to this service responses with the mapping of rooms and rates for a specified hotel

### Automated Inventory Management

Automate inventory operations by combining multiple BE-Connect-API endpoints. Agents can used to set rooms and rates availabilities and then used to set rooms and rates restrictions in a single workflow.

Example prompt: Call POST `/inventory/{hotel}/availabilities` to used to set rooms and rates availabilities, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call BE-Connect-API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'this service responses with the mapping of rooms and rates for a specified hotel', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/inventory/{hotel}` | this service responses with the mapping of rooms and rates for a specified hotel |
| POST | `/inventory/{hotel}/availabilities` | used to set rooms and rates availabilities |
| POST | `/inventory/{hotel}/restrictions` | used to set rooms and rates restrictions |
| POST | `/inventory/{hotel}/prices` | used to set rooms and rates prices |
| POST | `/planner/{hotel}` | used to retrieve the price planner |
| GET | `/reservations/{hotel}` | used to get all reservations that belong to certain hotel and are either receive |
| GET | `/reservations/{hotel}/{crsRefCode}` | used to get a single reservation details |
| GET | `/reservations/{hotel}/unread` | used to get all reservations that are either not acked or changed since the last |

## Key resources

- **Inventory** — Operations for inventory
- **Planner** — Operations for planner
- **Reservations** — Operations for reservations

## Why Jentic

- **Setup:** Wiring the BE-Connect-API by hand means learning its basic auth, choosing among the several BookingExpert Connect hosts, and handling the inventory, pricing, and reservation calls with retries yourself. Through Jentic you install once, import the BE-Connect-API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The API puts the hotel id in the URL path (`/inventory/{hotel}`, `/reservations/{hotel}`), so a rule can pin your agent to one hotel: it can work with that hotel's inventory and reservations and nothing else. You choose the operations it may call, so writing prices with POST `/inventory/{hotel}/prices` is not included unless you add it.
- **Credential handling:** Your BE-Connect-API basic 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.
- **Discovery method:** Agents search Jentic by intent such as 'read a hotel's reservations' or 'update room availability', and Jentic returns the matching BE-Connect-API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the BE-Connect-API use?

The BE-Connect-API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I this service responses with the mapping of rooms and rates for a specified hotel with the BE-Connect-API?

Yes. Use the GET `/inventory/{hotel}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the BE-Connect-API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I this service responses with the mapping of rooms and rates for a specified hotel through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'this service responses with the mapping of rooms and rates for a specified hotel'. Jentic returns the matching BE-Connect-API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the BE-Connect-API have?

The BE-Connect-API exposes 9 endpoints covering inventory, planner, reservations operations.

### Can I limit what my agent is allowed to do with the BE-Connect-API?

Yes. Because you run Jentic One yourself and set the rules, you decide which BE-Connect-API operations and credentials the agent may use. The hotel id sits in the URL path, so a rule can pin the agent to a single hotel's inventory and reservations and nothing else, and you can grant read-only calls like GET `/reservations/{hotel}` while withholding writes such as POST `/inventory/{hotel}/prices.` Only the operations you explicitly allow are callable.