Hubapi APIs
20 APIs151 Endpoints7 Categories
Categories
API Catalog(2 of 20)
HubSpot OAuth API
Jentic publishes the only available OpenAPI specification for HubSpot OAuth API, keeping it validated and agent-ready. This API exposes the token endpoints behind HubSpot's OAuth 2.0 flow — exchanging an authorization code or refresh token for an access token, inspecting an existing access or refresh token, and revoking a refresh token. It is the integration surface for any app that connects HubSpot accounts via OAuth instead of static keys.
4 endpointsVisitor Identification
Jentic publishes the only available OpenAPI specification for Visitor Identification, keeping it validated and agent-ready. The HubSpot Visitor Identification API issues short-lived tokens that link a verified, signed-in user from your own authentication system to the HubSpot chat widget. By passing the generated token to the widget, the chat session is associated with a known contact instead of an anonymous visitor, so conversation history and CRM context follow the user. The API exposes one endpoint, POST /conversations/v3/visitor-identification/tokens/create, which is called server-side after your application has authenticated the user.
1 endpointsConnect Your Agent
1
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 | sh2
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 instanceJentic 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.