canonical: https://jentic.com/apis/lobbytrack.com/lobbytrack # Lobbytrack API 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. ## For AI agents Manage employees, visitors, visits, locations, spaces, and bookings for an office visitor management workflow through the Lobbytrack API. ## Scope Does not handle payroll, badge printing hardware, or building access control - use for visitor management, sign-in, and desk or space booking only. ## Capabilities - Register and update employee records, including sign-in and sign-out events - 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 - Pull historical sign-in and sign-out data for employees and visitors for compliance reporting - Sync employee directories from an HR system into Lobbytrack on a schedule ## Use cases ### 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. Example prompt: 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'. Example prompt: 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. Example prompt: 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. Example prompt: 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 | Method | Path | Description | | --- | --- | --- | | POST | `/api/v1/visitors` | Register a new visitor | | 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 | ## Key resources - **Employees** — Manage employee records and retrieve sign-in/sign-out history - **Visitors** — Create and update visitor records - **Locations** — Manage office locations available for visits and bookings - **Spaces** — Define and manage rooms, desks, and other bookable spaces - **Space Types** — Group spaces by type (e.g., desk, meeting room) for booking rules - **Bookings** — Create and manage reservations against spaces ## Why Jentic - **Setup:** Wiring the Lobbytrack API by hand means setting up its Authorization key auth, attaching it to every call against api.lobbytrack.com, and handling retries yourself across visitor and booking operations. Through Jentic you install once, import the Lobbytrack API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Lobbytrack takes new visitors and employees in the request body while booking updates carry the id in the URL path, so limit the agent to the operations it needs, such as POST `/api/v1/visitors` or GET `/api/v1/spaces.` You choose the operations it may call, so employee creation with POST `/api/v1/employees` is not included unless you add it. - **Credential handling:** Your Lobbytrack API key is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header 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 'book a desk', 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 API** — Alternative visitor management and workplace platform with similar visitor, employee, and space coverage - **Google Analytics API** — Pair workplace footfall data from Lobbytrack with web analytics for unified visitor reporting - **BambooHR API** — Sync the BambooHR employee directory into Lobbytrack as the source of truth for sign-in ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Lobbytrack API? Yes. Because Jentic One is self-hosted, you run it yourself and your own rules decide which Lobbytrack operations and credentials the agent may use. You can scope the agent to just the calls it needs, such as POST `/api/v1/visitors` to register a guest or GET `/api/v1/spaces` to look up bookable desks, while excluding write operations like POST `/api/v1/employees` so the agent cannot create employee records unless you add that operation. The stored API key is injected only at execution time for the operations you have allowed, so the agent never gains access to endpoints outside that set.