Introducing the ALICE Visitor Management API

ALICE Receptionist now offers a visitor management API: the ALICE Developer API, a REST API with real-time webhooks that connects your visitor check-in data to the HR, security, and workflow tools your organization already uses.

With the API, your IT team can create visitor appointments from other systems and keep employee directories in sync. It can also trigger automated workflows the moment a visitor checks in or out. Because it works with Microsoft Power Automate, Zapier, and custom applications, visitor information moves where it’s needed without manual re-entry.

Here’s what the API does, how organizations can put it to work, and how to get started.

ALICE Visitor Management API at a Glance

What Does the ALICE Visitor Management API Do?

The ALICE Developer API gives approved applications secure, programmatic access to the core records behind your visitor management system. It covers three main areas.

Visitor appointments. Create, update, look up, and cancel visitor appointments from outside ALICE. A scheduling tool, CRM, or internal portal can pre-register guests automatically, so visitors are expected before they arrive.

Organization data. Manage the employees, departments, positions, companies, locations, and directories that power check-in and host lookup. Keeping these records current from a single source means visitors always reach the right person.

Real-time webhooks. Subscribe to visitor events and ALICE sends the details to your endpoint as they happen. Webhooks fire when an appointment is created, when a visitor checks in, and when a visitor checks out.

The API also provides access to restricted and denied entry events, and can send host notifications triggered by other systems.

How Organizations Can Use the Visitor Management API

The visitor management API covers the integrations IT teams commonly look for when evaluating visitor management software. Here are four practical ways to put it to work.

Keep employee directories in sync with HR

When someone joins, moves departments, or leaves, the visitor management directory should change too. The API lets an HR system or identity workflow update employees, departments, and positions in ALICE automatically. As a result, visitors only reach current staff, and front desk teams no longer maintain a second list by hand.

Send check-in alerts to the tools hosts already use

A check-in webhook can trigger a Power Automate flow that posts a message to a Microsoft Teams channel, or a Zapier workflow that alerts a Slack channel. Hosts and security teams see arrivals where they already work. ALICE also offers a native Microsoft Teams integration for host calls and alerts, and the API extends it with custom workflows.

Bring visitor activity into security reporting

Security and compliance teams can pull restricted and denied entry events into their own reporting tools. In addition, check-in and check-out webhooks give a real-time record of who is on site, which helps with audits, incident reviews, and occupancy tracking across locations.

Pre-register visitors from other systems

An interview scheduling tool, a contractor management platform, or a client portal can create ALICE appointments as soon as a visit is booked. That way, visitors are expected when they arrive, check-in is faster, and hosts get notified without anyone retyping visitor details.

Works With Power Automate and Zapier

Many teams can connect ALICE to other software without writing custom code. ALICE webhooks work with the workflow automation platforms IT teams already use.

Microsoft Power Automate. Use ALICE visitor events to start Power Automate flows when a visitor checks in, checks out, or has an appointment created. This is a natural fit for organizations on Microsoft 365, where flows can reach Teams, Outlook, SharePoint, and Excel.

Zapier. Use the Webhooks by Zapier trigger to catch ALICE events and pass them to thousands of other apps, from Slack and Google Sheets to ticketing and CRM platforms.

The ALICE Developer API portal includes step-by-step setup guides for both platforms. For broader options, including direct integrations with Microsoft Entra ID, SIP phone systems, and browser-based kiosk tools, see ALICE’s visitor management integrations.

Built for Secure Visitor Data

Visitor records include names, contact details, and on-site activity, so the API is designed to keep access controlled and verifiable.

• Token-based authentication. Applications sign in with issued credentials and receive an expiring JWT bearer token to use on every request.
• Scoped permissions. ALICE grants each application specific read or write permissions by resource, such as appointments, employees, or webhooks, so it can only reach the data it needs.
• Signed webhook deliveries. ALICE signs every webhook with HMAC-SHA256, so your systems can confirm each event came from ALICE before acting on it.

Together, these controls let IT and security teams connect visitor data to other systems.

How to Get Started With the ALICE API

Getting connected to the visitor management API takes three steps.

1. Request API credentials. Contact your ALICE account manager to register an API application. You’ll receive a client ID, a client secret, and your production base URL.
2. Authenticate. Exchange your credentials for a token, then include it with each request.
3. Build your integration. Create your first appointment, subscribe to webhooks, or follow the Power Automate and Zapier guides.

Full documentation, including the API reference, code samples, and the webhook payload format, is available in the ALICE Developer API portal.

Not a customer yet? Integration requirements are a common part of visitor management evaluations. Our team can walk through how ALICE would connect to your environment during a personalized demo.