HubSpot Visitor Identification

Name: Visitor Identification API
Brand: Visitor Identification
Availability: InStock

✓ Official Vendor SpecCommunicationsChat Messagingoauth2, apiKey1 EndpointsREST

For Agents

Generate identification tokens that link an authenticated user to the HubSpot chat widget so chat sessions are tied to a known contact. Useful for agents wiring up SSO chat experiences.

Use for: Generate a HubSpot visitor identification token for a logged-in user, Issue a chat widget token tied to an authenticated email, Check whether a visitor token can be issued for a given user, Refresh a HubSpot chat identification token when it expires

Not supported: Does not authenticate users, send chat messages, or manage CRM contacts - use for issuing HubSpot chat widget identification tokens only.

The HubSpot Visitor Identification API issues short-lived identification tokens that pass authenticated visitor identity into the HubSpot chat widget. It accepts an email and friendly name from your own authentication system, and returns a token that the HubSpot chat widget consumes so the chat session is associated with a known contact rather than an anonymous visitor. This is the primary surface for identified-visitor chat experiences on HubSpot-hosted and embedded chat widgets.

Install Jentic One Beta

Connect the Visitor Identification to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Visitor Identification, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-conversations-visitor-identification" | sh

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%2Fhubspot.com%2Fhubspot-conversations-visitor-identification" | 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 Visitor Identification API.

Generate a HubSpot visitor identification token from an email and friendly name

Return a token suitable for the HubSpot chat widget identifyVisitor call

Pair authenticated visitors from an external SSO with HubSpot contact records

Issue short-lived tokens that expire to limit replay risk

Use Cases

Patterns agents use Visitor Identification API for, with concrete tasks.

GET STARTED

Start building with Visitor Identification API

Explore with Jentic One

View OpenAPI Document

SSO Chat Bridging

Bridge a single sign-on session into HubSpot chat by minting an identification token after the SSO handshake. Useful for B2B portals where every chat user is already authenticated and the support team needs the conversation tied to a known account immediately.

After SSO success, POST /visitor-identification/v3/tokens/create with the authenticated email and name, and return the token to the chat widget.

High-Trust Support Channels

Reduce verification friction for known account holders by stamping every chat session with an identification token. Reps see the matching CRM record automatically, and chat history persists across sessions without prompting visitors to re-enter contact details.

POST /visitor-identification/v3/tokens/create with the verified user's email and name when they navigate to the support page.

Agent-Issued Chat Tokens

Use Jentic to issue HubSpot identification tokens from an AI agent without embedding HubSpot SDK code in the application. The agent invokes the token-issue operation by intent, and the HubSpot OAuth or private app token used to call HubSpot stays in your Jentic One instance.

Use Jentic search 'generate a HubSpot visitor identification token', load the POST /visitor-identification/v3/tokens/create schema, and execute with email and friendly name.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring HubSpot Visitor Identification by hand means learning its OAuth2 access token or private app token auth, targeting the api.hubapi.com host, and posting the identification token request yourself. Through Jentic you install once, import HubSpot Visitor Identification from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Visitor Identification API takes the visitor's email and details in the request body, so limit the agent to the operations it needs, such as creating a chat identification token. You choose which operations are allowed, and here the single token-create call is the only operation this API exposes.

Credential isolation

Your HubSpot access token or private app token 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 'generate a chat identification token', and Jentic returns the matching POST /visitor-identification/v3/tokens/create operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Visitor Identification API through Jentic.

What authentication does the HubSpot Visitor Identification API use?

OAuth 2.0 authorization code flow or a private app token in the `private-app-legacy` header. Through Jentic, the credential is held encrypted in the vault and the agent only sees a scoped execution token.

Can I tie a logged-in user to a HubSpot contact via this API?

Yes. POST /visitor-identification/v3/tokens/create accepts an email and friendly name and returns a token. Pass it to the chat widget's `identificationToken` setting so HubSpot links the session to the contact matching that email.

What are the rate limits for the Visitor Identification API?

Standard HubSpot API limits apply - roughly 100 requests per 10 seconds per OAuth app. Issue tokens on demand at session start rather than for every page navigation to avoid hitting the per-second ceiling.

How do I issue a token through Jentic?

Search Jentic for `generate a HubSpot visitor identification token`, load the POST /visitor-identification/v3/tokens/create schema, and execute with the user's email and name. Install with `pip install jentic` and authenticate using `JENTIC_AGENT_API_KEY`.

How long does an identification token stay valid?

HubSpot issues short-lived tokens intended for a single chat session - they typically expire within hours. Mint a fresh token at session start rather than caching one across sessions.

Can I limit what my agent is allowed to do with the HubSpot Visitor Identification API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. This API exposes a single operation, POST /visitor-identification/v3/tokens/create, so you can allow just that token-create call and nothing else. Your HubSpot OAuth or private app token stays in your own instance and is injected only when the agent runs the operation you permitted.