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.

Quickstart

Get started with Visitor Identification in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"generate a HubSpot visitor identification token"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

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

GET STARTED

Start building with Visitor Identification API

Explore with Jentic

View OpenAPI Document

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.

★ Authenticated Chat for Logged-In Customers

When a customer is signed into your portal, call POST /visitor-identification/v3/tokens/create with their email and name to mint a token. Pass the token to the HubSpot chat widget's identifyVisitor call so the chat session is tied to the matching HubSpot contact, allowing reps to see history without verifying identity again.

On portal login, POST /visitor-identification/v3/tokens/create with the user's email and friendly name, then return the token to the front-end for `hsConversationsSettings.identificationToken`.

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 the Jentic vault.

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.

Key Endpoints

1 endpoints — the hubspot visitor identification api issues short-lived identification tokens that pass authenticated visitor identity into the hubspot chat widget.

METHOD

PATH

DESCRIPTION

POST

/visitor-identification/v3/tokens/create

Generate a visitor identification token

POST

/visitor-identification/v3/tokens/create

Generate a visitor identification token

Why though Jentic?

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

Credential isolation

HubSpot OAuth and private app tokens for Visitor Identification are stored encrypted in the Jentic vault. The agent receives only a scoped execution token; the raw HubSpot credential never enters its prompt.

Intent-based discovery

Agents search Jentic with intents like 'generate a chat identification token' and Jentic returns the matching POST /visitor-identification/v3/tokens/create operation with its input schema, ready to call.

Time to first call

Direct integration including OAuth and front-end widget wiring takes about a day. Through Jentic: under 30 minutes for the back-end token issue step.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot Conversations Inbox & Messages

Read and reply within the inbox that an identified chat lands in.

Use Conversations-conversationsInboxMessages when the agent needs to read or respond to threads from the identified visitors.

Complementary

HubSpot CRM Contacts

Look up or create the contact that an identification token is tied to.

Pick CRM-contacts when the agent needs to confirm a contact exists in the CRM before issuing an identification token.

Complementary

HubSpot Conversations Custom Channels

Surface external chat channels alongside identified-visitor chat.

Use Conversations-customChannels when the agent must register a non-native channel that complements the identified chat widget.

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.