canonical: https://jentic.com/apis/api.lobbytrack.com/lobbytrack

# Lobbytrack API

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.

## For AI 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.

## Scope

Does not handle door hardware control, video surveillance, or payroll. Use for visitor and workplace access management only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Add a new employee and confirm the location they are based at

## Key endpoints

| 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 |

## Key resources

- **Visitors and visits** — Register visitors, create visits, and record sign-ins, sign-outs, and agreements
- **Employees and locations** — Manage employees, locations, spaces, and space types
- **Bookings** — Create and manage room and space bookings

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Envoy** — Visitor and workplace management compared with Lobbytrack
- **Robin** — Desk and room booking that pairs with Lobbytrack's visitor tracking
- **Verkada** — Physical access control alongside Lobbytrack's visitor records

## FAQ

### 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.