canonical: https://jentic.com/apis/swaggerhub.bookingexpertapi/bebe-access

# Bookingexpertapi BEBE Access

BookingExpert BookingEngine Access Manager. The API exposes 47 endpoints.

## For AI agents

Programmatically get all users repositories, get a single users repository. Covers 47 operations.

## Scope

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

## Capabilities

- get all users repositories
- create a users repository
- update a users repository
- delete a users repository
- insert a user in a users repository for a defined application

## Use cases

### E-Commerce Operations

Use the BEBE Access to perform e commerce operations programmatically. The API provides 47 endpoints covering core functionality including get all users repositories, get a single users repository, create a users repository.

Example prompt: Call GET `/repository/getall` to get all users repositories

### Automated repositories Management

Automate repositories operations by combining multiple BEBE Access endpoints. Agents can get a single users repository and then create a users repository in a single workflow.

Example prompt: Call GET `/repository/read` to get a single users repository, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call BEBE Access 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 'get all users repositories', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/repository/getall` | get all users repositories |
| GET | `/repository/read` | get a single users repository |
| GET | `/repository/insert` | create a users repository |
| GET | `/repository/update` | update a users repository |
| GET | `/repository/delete` | delete a users repository |
| GET | `/user/insert` | insert a user in a users repository for a defined application |
| GET | `/user/delete` | delete a user by his username for a defined application |
| GET | `/user/login` | check user credentials in a users repository for a defined application |

## Key resources

- **repositories** — Operations to manage users repositories
- **users** — Operations to manage users
- **recoveries** — Operations to manage recoveries
- **versions** — Operations to manage hotel versions
- **spf** — Operation to check SPF

## Why Jentic

- **Setup:** Wiring the BEBE Access API by hand means mapping its repository and user endpoints, formatting each read and write call, and handling retries yourself. Through Jentic you install once, import the BEBE Access API from the API Directory, and your agent calls it without you writing that plumbing.
- **Permission scoping:** The repository and user operations carry their target in the request rather than a resource id in the URL path, so scope the agent to the operations it needs, such as reading records with `/repository/read.` You choose the allowed set, so deleting a record with `/repository/delete` is not included unless you add it.
- **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 'read an access record' or 'create a user', and Jentic returns the matching BEBE Access 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 BEBE Access use?

The BEBE Access 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 get all users repositories with the BEBE Access?

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

### What are the rate limits for the BEBE Access?

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 get all users repositories through Jentic?

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

### How many endpoints does the BEBE Access have?

The BEBE Access exposes 47 endpoints covering repositories, users, recoveries operations.

### Can I limit what my agent is allowed to do with the BEBE Access API?

Yes. Because you run Jentic One yourself and self-host it, your own rules decide which BEBE Access operations and credentials the agent may use. Since the repository and user operations name their target in the request rather than in the URL path, you scope the agent to just the calls it needs, such as reading records with GET `/repository/read`, and destructive calls like GET `/repository/delete` or GET `/user/delete` stay out of reach unless you explicitly add them.