Bookingexpertapi BEBE Access
Browse all Swaggerhub Bookingexpertapi APIsCommunity OpenAPI document · agent-readyE CommerceStorefrontnone47 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically get all users repositories, get a single users repository. Covers 47 operations.
Use for: I need to all users repositories, I want to a single users repository, Search for a users repository, Find all a users repository
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
BookingExpert BookingEngine Access Manager. The API exposes 47 endpoints.
Install Jentic One Beta
Connect the BEBE Access to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BEBE Access, 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%2Fswaggerhub.bookingexpertapi%2Fbebe-access" | 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%2Fswaggerhub.bookingexpertapi%2Fbebe-access" | 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.
Capabilities
What an agent can do with BEBE Access API.
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
Patterns agents use BEBE Access API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'get all users repositories', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
47 endpoints — bookingexpert bookingengine access manager.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using BEBE Access API through Jentic.
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.
GET STARTED