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

# Bookingexpertapi BE-WS

API to retrieve information about the booking engine configuration. The API exposes 2 endpoints.

## For AI agents

Programmatically getroom, getoffer. Covers 2 operations.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- getRoom
- getOffer
- Integrate BE-WS into automated workflows
- Query and filter BE-WS records by parameters
- Monitor BE-WS operational status and events

## Use cases

### E-Commerce Operations

Use the BE-WS to perform e commerce operations programmatically. The API provides 2 endpoints covering core functionality including getroom, getoffer.

Example prompt: Call GET /rooms to getroom

### Data Retrieval and Monitoring

Query BE-WS resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary BE-WS endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call BE-WS 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 none tokens manually.

Example prompt: Search Jentic for 'getroom', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/rooms` | getRoom |
| GET | `/offers` | getOffer |

## Key resources

- **Offers** — Operations for offers
- **Rooms** — Operations for rooms

## Why Jentic

- **Setup:** Wiring the BE-WS API by hand means mapping its rooms and offers endpoints, choosing among the BookingExpert booking hosts, and handling retries yourself. Through Jentic you install once, import the BE-WS API from the API Directory, and your agent calls it without you writing that plumbing.
- **Permission scoping:** The rooms and offers reads carry their filters in the request rather than a resource id in the URL path, so scope the agent to the operations it needs, such as listing rooms with GET /rooms and offers with GET /offers. The agent runs only the operations you allow.
- **Credential handling:** This spec defines no authentication, so there is no credential to store. If you point it at a host that adds a key later, that key is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list available rooms' or 'get current offers', and Jentic returns the matching BE-WS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the BE-WS use?

The BE-WS uses no authentication. 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 getroom with the BE-WS?

Yes. Use the GET /rooms endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the BE-WS?

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 getroom through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getroom'. Jentic returns the matching BE-WS operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the BE-WS have?

The BE-WS exposes 2 endpoints covering offers, rooms operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which BE-WS operations and credentials the agent may use. You can scope it to just the reads it needs, such as listing rooms with GET /rooms or fetching offers with GET /offers, and leave everything else off. The agent runs only the operations you allow.