Bookingexpertapi BE Identity

Name: BE Identity API
Brand: BE Identity
Availability: InStock

Browse all Swaggerhub Bookingexpertapi APIs

★ Only Publicly Available OpenAPI DocumentIdentity AuthDirectory Servicesnone34 Endpoints

Install Jentic One Beta

Connect the BE Identity to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BE Identity, 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%2Fswaggerhub.bookingexpertapi%2Fbe-identity" | 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%2Fswaggerhub.bookingexpertapi%2Fbe-identity" | 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 BE Identity API.

get all users repositories

create a users repository

update a users repository

delete a users repository

GET STARTED

Start building with BE Identity API

Explore with Jentic One

View OpenAPI Document

For Agents

Programmatically get all users repositories, get a single users repository. Covers 34 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 identity and authentication only.

Use Cases

Patterns agents use BE Identity API for, with concrete tasks.

★ Identity and Authentication Operations

Use the BE Identity to perform identity auth operations programmatically. The API provides 34 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 BE Identity 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 BE Identity 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

34 endpoints — bookingexpert identity 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

Why Jentic?

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

Setup

Wiring the BE Identity 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 BE Identity 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 users with /repository/read. You choose the allowed set, so deleting a user with /user/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 'look up a user record' or 'log a user in', and Jentic returns the matching BE Identity operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using BE Identity API through Jentic.

What authentication does the BE Identity use?

The BE Identity 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 BE Identity?

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 BE Identity?

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 BE Identity operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the BE Identity have?

The BE Identity exposes 34 endpoints covering repositories, users, recoveries operations.

Can I limit what my agent is allowed to do with the BE Identity API?

Yes. Because you run Jentic One yourself, your own rules decide which BE Identity operations and credentials the agent may use, and you allow only the ones it needs. Since these repository and user operations carry their target in the request rather than a resource id in the URL path, you can grant read-only calls such as GET /repository/read or GET /repository/getall while withholding destructive ones. Deleting a user with GET /user/delete or removing a repository with GET /repository/delete stays out of the agent's reach unless you explicitly add it.

Bookingexpertapi BE Identity

Connect the BE Identity to your agent

Capabilities

Start building with BE Identity API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs