Envoy Visitor Management API

Name: Envoy Visitor Management API
Brand: Envoy Visitor Management API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationbearer19 EndpointsREST

For Agents

Read visitor entries, manage employee invitations and work schedules, and sync locations and reservations from the Envoy workplace platform.

Install Jentic One Beta

Connect the Envoy Visitor Management API to your agent

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

Step 1: 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

Step 2: 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 Envoy Visitor Management API.

List visitor entries and retrieve a single entry by ID for reporting and audit trails

Read and look up flows that determine the sign-in experience for different visitor types

Read locations and companies via the rest/v1 endpoints to align Envoy data with internal directories

GET STARTED

Start building with Envoy Visitor Management API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Envoy Visitor Management API for, with concrete tasks.

★ Visitor Sign-In Audit and Reporting

Pull entries with GET /v1/entries on a schedule into a data warehouse or compliance report so security and facilities teams have a complete record of who visited each location. Combine with /v1/flows to label each entry by visit type. Useful for SOC 2 and similar audits that require visitor logs.

Call GET /v1/entries with the desired date range and load the results into the warehouse table for compliance reporting.

Pre-Registered Visitor Invitations

When an external system schedules a meeting, create an Envoy invitation via POST /v1/invitations so the visitor's name and arrival time are pre-loaded at the front desk. Update or cancel the invitation if the meeting changes via PUT or DELETE on /v1/invitations/{id}. This integration removes manual front-desk entry and shortens visitor wait time.

Submit POST /v1/invitations with the visitor's name, email, and arrival time, then store the returned invitation ID against the meeting record.

Employee and Work Schedule Sync

Read employee records via GET /v1/employees and pull schedules via GET /v1/work-schedules to feed office attendance dashboards and capacity-planning tools. Pair with HR data to detect mismatches between the Envoy directory and the source-of-truth HRIS so people-ops can keep records aligned.

Pull GET /v1/employees and reconcile email addresses against the HRIS to surface any employees missing from Envoy.

AI Agent Workplace Assistant Through Jentic

An AI workplace assistant uses Jentic to discover Envoy operations by intent and answers questions like 'who is visiting today?' or 'register Jane as a guest at 2pm' by chaining /v1/entries reads with /v1/invitations writes. The Envoy bearer token stays in the Jentic vault and never enters the agent's prompt context.

Search Jentic for 'register a visitor in Envoy', load POST /v1/invitations, and execute it with the visitor's details for tomorrow's meeting.

Key Endpoints

19 endpoints — envoy is a workplace platform that handles visitor sign-in, deliveries, room and desk reservations, and employee scheduling.

METHOD

PATH

DESCRIPTION

GET

/v1/entries

List visitor entries

GET

/v1/entries/{id}

Get a single entry by ID

GET

/v1/flows

List sign-in flows

POST

/v1/invitations

Create a pre-registered visitor invitation

PUT

/v1/invitations/{id}

Update an invitation

DELETE

/v1/invitations/{id}

Delete an invitation

GET

/v1/employees

List employees

GET

/v1/work-schedules

List work schedules

GET

/v1/entries

List visitor entries

GET

/v1/entries/{id}

Get a single entry by ID

GET

/v1/flows

List sign-in flows

POST

/v1/invitations

Create a pre-registered visitor invitation

PUT

/v1/invitations/{id}

Update an invitation

DELETE

Why Jentic?

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

Credential isolation

Envoy bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents call /v1/entries, /v1/invitations, /v1/employees, and the rest/v1 endpoints through scoped tokens — the bearer value never enters the agent's prompt context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'pre-register a visitor in Envoy') and receive the matching Envoy operation with its input schema, so the agent calls POST /v1/invitations without scraping the developer hub.

Time to first call

Direct Envoy integration: 1-2 days to wire up auth, invitation lifecycle, and entry sync into a warehouse. Through Jentic: about an hour — search, load, execute.

FAQs

Specific to using Envoy Visitor Management API through Jentic.

What authentication does the Envoy API use?

The Envoy API uses HTTP bearer token authentication. Each request must include an Authorization header with a bearer token issued from the Envoy dashboard. Through Jentic, the token is stored encrypted in the vault (MAXsystem) and injected at execution time so it never enters the agent context.

Can I pre-register visitors with the Envoy API?

Yes. POST /v1/invitations creates an invitation that pre-loads the visitor's information at the front desk. PUT /v1/invitations/{id} updates the invitation and DELETE /v1/invitations/{id} cancels it. This is the supported way to integrate scheduling systems with Envoy.

How do I list visitor entries?

Call GET /v1/entries with the desired date and location filters. For a single entry, GET /v1/entries/{id} returns the full record. The endpoints back compliance reporting and visitor analytics flows.

What are the rate limits for the Envoy API?

The OpenAPI spec does not publish numeric rate limits. Envoy applies plan-based throttling at the account level — contact Envoy support if your integration needs sustained high-throughput access for entry sync or large bulk operations.

How do I create a visitor invitation through Jentic?

Search Jentic for 'create a visitor invitation in Envoy', load POST /v1/invitations, and execute it with the visitor's name, email, and arrival time. Get started at https://app.jentic.com/sign-up.

Does the Envoy API expose work schedules and reservations?

Yes. The Work Schedules and Reservations tags expose read endpoints for employee schedules and desk/room reservations, supporting office attendance reporting and capacity planning workflows.

Envoy Visitor Management API

Connect the Envoy Visitor Management API to your agent

Capabilities

Start building with Envoy Visitor Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs