Flexopus API

Name: Flexopus API
Brand: Flexopus API
Availability: InStock

✓ Official Vendor SpecProductivityCalendar Schedulingbearer20 EndpointsREST

For Agents

Book hybrid-workplace desks, rooms, and parking spaces, and read occupancy and event data from a tenant's Flexopus instance.

Install Jentic One Beta

Connect the Flexopus API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flexopus API, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Flexopus API.

Reserve desks, rooms, and parking spaces on behalf of named users or by email lookup

Read live and historical bookings for a building, location, or individual bookable asset

Query current occupancy across all bookables in a location for floor-plan visualization

GET STARTED

Start building with Flexopus API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Flexopus API for, with concrete tasks.

★ Hybrid-work desk booking assistant

Employees use a chat or voice assistant to reserve desks, rooms, or parking spaces without opening the Flexopus web app. The assistant calls /api/v1/bookings to create the reservation and /api/v1/locations/{location_id}/bookables/occupancy to suggest a floor with availability, then confirms the booking with the user. This collapses a multi-click flow into a single sentence.

Reserve any free desk on the 3rd floor of the London office for tomorrow 09:00-17:00 for the authenticated user

Office occupancy reporting

Operations and facilities teams pull bookings and occupancy data into BI dashboards to track which floors and buildings are actually being used. The /api/v1/buildings/{building_id}/bookings and /api/v1/locations/{location_id}/bookables/occupancy endpoints return the raw activity needed to plan space contracts, identify under-used zones, and right-size the real estate footprint.

Pull yesterday's booking counts for every building and write the results to a CSV grouped by location

HR system user synchronization

When an HRIS adds, updates, or removes employees, those changes propagate into Flexopus through /api/v1/users/import and /api/v1/users/export. The bulk endpoints keep the workspace booking directory in sync with the source-of-truth identity system, which prevents stranded accounts and broken bookings when staff turn over.

Import a CSV of 50 new joiners and disable any user not present in the source export

AI agent meeting-room scheduler

An AI scheduling agent receives a request such as 'book the team a room with a whiteboard for Thursday 2pm' and uses Flexopus to find an eligible bookable, create the booking, and add attendees. Through Jentic the agent searches by intent rather than browsing the 20-endpoint API surface, so the same scheduling skill works across multiple Flexopus tenants.

Find a bookable room with capacity 8 in the Berlin building, reserve it for Thursday 14:00-15:00, and add three named attendees

Key Endpoints

20 endpoints — the flexopus api provides programmatic access to a hybrid workplace booking platform that covers desks, meeting rooms, parking spaces, and other shared resources.

METHOD

PATH

DESCRIPTION

POST

/api/v1/bookings

Create a new desk, room, or parking booking

GET

/api/v1/bookings/{id}

Retrieve a specific booking

GET

/api/v1/locations/{location_id}/bookables/occupancy

Get live occupancy for all bookables in a location

GET

/api/v1/buildings/{building_id}/bookings

List bookings for a building

POST

/api/v1/users/import

Bulk import users into the tenant

GET

/api/v1/events/today

List events happening in the office today

GET

/api/v1/users/by-email/{user_email}/bookings

List bookings for a user looked up by email

POST

/api/v1/bookings

Create a new desk, room, or parking booking

GET

/api/v1/bookings/{id}

Retrieve a specific booking

GET

/api/v1/locations/{location_id}/bookables/occupancy

Get live occupancy for all bookables in a location

GET

/api/v1/buildings/{building_id}/bookings

List bookings for a building

POST

/api/v1/users/import

Bulk import users into the tenant

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Flexopus bearer tokens and the per-tenant subdomain are stored in the encrypted Jentic vault. Agents call by intent and Jentic injects the right token and base URL at execution time, so the raw credentials never enter the agent context.

Intent-based discovery

Agents search Jentic by intent such as 'book a meeting room' and Jentic returns the matching Flexopus operation with its input schema, removing the need to browse the 20-endpoint surface manually.

Time to first call

Direct Flexopus integration: 1-2 days for token handling, subdomain configuration, and bookable lookup logic. Through Jentic: under 1 hour to search, load the schema, and execute.

FAQs

Specific to using Flexopus API through Jentic.

What authentication does the Flexopus API use?

The Flexopus API uses HTTP bearer tokens. Through Jentic the bearer token is held in the encrypted vault and injected into the Authorization header at execution time, so the agent never sees the raw secret.

Can I book a desk with the Flexopus API?

Yes. POST to /api/v1/bookings with the bookable identifier and time window to reserve a desk, room, or parking space. Reservations can be created on behalf of any user the token has rights over.

How do I look up a colleague's bookings by email?

Call GET /api/v1/users/by-email/{user_email}/bookings. This is useful when an assistant only knows the user's email rather than their internal Flexopus ID.

What are the rate limits for the Flexopus API?

Flexopus does not document a fixed quota in the spec. Limits are applied per tenant and per token, so handle 429 responses by backing off using the Retry-After header.

How do I create a desk booking with the Flexopus API through Jentic?

Search Jentic for 'book a desk', load the schema for POST /api/v1/bookings, and execute the call with the bookable_id and time window. Install with pip install jentic and sign up at https://app.jentic.com/sign-up.

Does the Flexopus API support multiple offices?

Yes. Each Flexopus tenant runs on its own subdomain configured via the {flexopus-domain} server variable, and bookings are scoped to buildings and locations within that tenant.

Flexopus API

Connect the Flexopus API to your agent

Capabilities

Start building with Flexopus API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs