Lobbytrack API

Name: Lobbytrack API API
Brand: Lobbytrack API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar SchedulingapiKey46 EndpointsREST

For Agents

Manage employees, visitors, visits, locations, spaces, and bookings for an office visitor management workflow through the Lobbytrack API.

Connect the Lobbytrack API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lobbytrack 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.

Install Jentic One Beta (Self-Hosted)

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

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 Lobbytrack API API.

Create, update, and cancel visitor records and the visits attached to them

Manage office locations, spaces, and the space types used for desk and room booking

Create and modify desk or room bookings against a specific space and time slot

GET STARTED

Start building with Lobbytrack API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Lobbytrack API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Lobbytrack API, keeping it validated and agent-ready. Lobbytrack is a visitor management platform used by offices to register visitors, manage employees, book rooms and desks, and track sign-ins and sign-outs. The API exposes the full data model: employees, visitors, visits, locations, spaces, space types, and bookings. Office administrators use it to sync HR systems, expose a custom check-in flow, or automate desk-booking workflows.

Use Cases

Patterns agents use Lobbytrack API API for, with concrete tasks.

★ Custom Visitor Pre-Registration Portal

Companies often want their own branded visitor pre-registration form on their website rather than the default Lobbytrack one. The API lets a custom front end create a visitor record, attach a visit to a host employee, and set the location ahead of arrival. When the visitor turns up at reception, Lobbytrack already has them.

Call POST /api/v1/visitors with the visitor's name and contact info, then POST /api/v1/bookings or the visit endpoint to attach them to a host employee at a specific location.

Desk Booking Automation

Hybrid offices need flexible desk booking. The Lobbytrack API exposes spaces and space types to model the office floor plan, plus a bookings endpoint that creates, updates, and cancels reservations against a specific space and time. A team-channel bot can call this whenever an employee says 'book me a desk for tomorrow'.

Look up an available space via GET /api/v1/spaces, then POST /api/v1/bookings with the employee ID, space ID, and time window for tomorrow.

HR System Employee Sync

When HR adds a new starter, Lobbytrack needs the same employee record so the new person can sign in on day one. A scheduled sync calls POST /api/v1/employees for new hires and PATCH for changes. The same job can offboard leavers.

Compare the HR roster against GET /api/v1/employees, then POST new hires and PATCH any changed records.

AI Agent Office Concierge

A workplace AI agent can handle visitor and desk requests in chat: register a visitor, book a desk, look up who's in the office. Through Jentic the agent searches for the right Lobbytrack operation, loads the schema, and executes — without ever holding the API key.

Use Jentic to call POST /api/v1/visitors and POST /api/v1/bookings to register a guest and assign them a meeting room when the user types 'I have a guest at 2pm'.

Key Endpoints

46 endpoints — jentic publishes the only available openapi specification for lobbytrack api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/visitors

POST

/api/v1/bookings

Create a booking against a space

GET

/api/v1/employees/signins

List employee sign-in events

POST

/api/v1/employees

Add a new employee record

GET

/api/v1/spaces

List bookable spaces

PATCH

/api/v1/bookings/{bookingId}

Update an existing booking

POST

/api/v1/visitors

POST

/api/v1/bookings

Create a booking against a space

GET

/api/v1/employees/signins

List employee sign-in events

POST

/api/v1/employees

Add a new employee record

GET

/api/v1/spaces

List bookable spaces

Why though Jentic?

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

Credential isolation

Lobbytrack API keys are stored encrypted in the Jentic vault. The Authorization header is injected at execution time, so the raw key never enters the agent context, logs, or LLM traces.

Intent-based discovery

Agents search Jentic for intents like 'register a visitor' or 'book a desk' and Jentic returns the matching Lobbytrack operation with its input schema, so the agent can act on natural-language workplace requests without browsing API docs.

Time to first call

Direct Lobbytrack integration: 2-3 days for auth, modelling spaces and space types, and wiring booking flows. Through Jentic: under 1 hour to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Envoy API

Alternative visitor management and workplace platform with similar visitor, employee, and space coverage

Choose Envoy when the team is already using Envoy for visitor sign-in, deliveries, and desk booking, or wants a broader workplace ecosystem.

Complementary

Google Analytics API

Pair workplace footfall data from Lobbytrack with web analytics for unified visitor reporting

Use Google Analytics alongside Lobbytrack when the agent needs to combine physical office footfall with digital visitor data in a single dashboard.

Complementary

BambooHR API

Sync the BambooHR employee directory into Lobbytrack as the source of truth for sign-in

Use BambooHR when the agent needs HR-system records as the master, with Lobbytrack handling the office-presence layer.

FAQs

Specific to using Lobbytrack API API through Jentic.

Why is there no official OpenAPI spec for Lobbytrack API?

Lobbytrack does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Lobbytrack API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Lobbytrack API use?

Lobbytrack uses an API key passed in the Authorization header on every request. Through Jentic, the key is held encrypted in the vault and injected at execution time, so the raw value never reaches the agent's context.

Can I create a visitor and attach them to a host employee in one workflow?

Yes. POST /api/v1/visitors creates the visitor record. Bookings and visits are then attached to that visitor for a specific employee and location. The employee acts as the host and shows up on the visitor's pass.

What are the rate limits for the Lobbytrack API?

Rate limits are not declared in the spec. Lobbytrack applies plan-level limits to API throughput; check your account portal or contact support for the limits attached to your tier.

How do I book a desk for an employee through Jentic?

Search Jentic for 'book a desk for an employee'. Jentic returns the POST /api/v1/bookings operation. Load the schema, supply the employee ID, space ID, and time window, and execute. The response includes the booking ID.

Can I list everyone currently signed in at a particular location?

Yes. Use GET /api/v1/employees/signins for employee sign-ins and the visitors sign-in endpoints for visitors. Filter by location to get the people present at a specific office.