Lobbytrack API
Official vendor OpenAPI document · agent-readyProductivityCalendar SchedulingapiKey46 EndpointsREST
For Agents
Register visitors, create visits, and record sign-ins and sign-outs for a workplace. Manage employees, locations, spaces, visitor types, and room bookings across the front desk.
Use for: Register a visitor for an upcoming visit, Sign in a visitor at the front desk, Create a booking for a meeting space, List the visitors expected at a location
Not supported: Does not handle door hardware control, video surveillance, or payroll. Use for visitor and workplace access management only.
The Lobbytrack API manages workplace visitors, employees, and the visits between them, covering sign-ins, sign-outs, and visitor agreements. It also handles locations, spaces, space types, visitor types, and room bookings, so an agent can run front-desk and workplace access workflows without manual data entry.
Install Jentic One Beta
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.
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%2Fapi.lobbytrack.com%2Flobbytrack" | 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%2Fapi.lobbytrack.com%2Flobbytrack" | 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 Lobbytrack API.
Register and manage visitors and their visitor types
Create and track visits, including sign-ins, sign-outs, and visitor agreements
Manage employees and their sign-in and sign-out records
Manage locations, spaces, and space types across the workplace
Create and manage room and space bookings
Retrieve the visitor agreements tied to a visit
Use Cases
Patterns agents use Lobbytrack API for, with concrete tasks.
★ Front-Desk Visitor Agent
An AI agent handles arrivals by registering the visitor, creating the visit, and recording the sign-in, then surfacing the visitor agreement that needs acceptance. Through Jentic the agent discovers the visitor and visit operations by intent and calls them directly, so reception runs without a person keying each arrival.
Register an expected visitor, create their visit, and record the sign-in on arrival
Workplace Booking Management
Manage room and space reservations by listing spaces, checking space types, and creating bookings. The agent can hold a meeting room for a visit or free it when plans change, keeping the workplace schedule current without a manual booking tool.
Create a booking for a meeting room to match a scheduled visitor arrival
Employee and Location Directory
Keep the people and places behind visits accurate by managing employees, locations, and spaces. This lets an agent resolve the right host and location before a visit is created, so sign-ins map to real employees and rooms.
Add a new employee and confirm the location they are based at
Key Endpoints
46 endpoints — the lobbytrack api manages workplace visitors, employees, and the visits between them, covering sign-ins, sign-outs, and visitor agreements.
METHOD
PATH
DESCRIPTION
POST
/api/v1/visitors
Register a visitor
GET
/api/v1/visitors
List visitors
GET
/api/v1/visitors/signins
List visitor sign-ins
GET
/api/v1/employees
List employees
POST
/api/v1/employees
Add an employee
POST
/api/v1/visitors
Register a visitor
GET
/api/v1/visitors
List visitors
GET
/api/v1/visitors/signins
List visitor sign-ins
GET
/api/v1/employees
List employees
POST
/api/v1/employees
Add an employee
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Lobbytrack API by hand means handling its Authorization-header API key and the register then visit then sign-in sequence yourself. Through Jentic you install once, import Lobbytrack from the API Directory, store the key once, and your agent calls it.
Permission scoping
Lobbytrack identifies visitors, employees, and visits by an id in the request path, so a rule bounds which operations your agent may call. You choose those operations, so destructive ones like deleting a visitor or employee are not included unless you add them.
Credential isolation
Your Lobbytrack API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'register a visitor' or 'create a booking', and Jentic returns the matching Lobbytrack 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.
FAQs
Specific to using Lobbytrack API through Jentic.
What authentication does the Lobbytrack API use?
The Lobbytrack API authenticates with an API key sent in the Authorization header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.
Can I sign a visitor in with the Lobbytrack API?
Yes. Register the visitor with POST /api/v1/visitors, create their visit, and use the visit sign-in operation to record arrival. GET /api/v1/visitors/signins lists recent sign-ins for a location.
What are the rate limits for the Lobbytrack API?
The OpenAPI spec does not specify rate limits. Check the Lobbytrack documentation at https://api.lobbytrack.com/swagger before running high-volume sync jobs.
Is there a Lobbytrack MCP server?
You don't need an MCP server to give your agent the Lobbytrack API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the visitor and visit operations it needs.
Can I limit what my agent is allowed to do with the Lobbytrack API?
Yes. Write a rule that allows only the visitor and visit operations, so the agent can register arrivals and record sign-ins but cannot delete employees or visitors, and every call it makes is logged.
How do I register a visitor with the Lobbytrack API through Jentic?
Search Jentic for 'register a visitor', and it returns the POST /api/v1/visitors and visit operations with their input schemas so your agent handles the arrival directly. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED