Hubapi APIs

20 APIs151 Endpoints7 Categories

API Catalog(3 of 20)

Custom Behavioral Events API

Jentic publishes the only available OpenAPI specification for Custom Behavioral Events API, keeping it validated and agent-ready. HubSpot's Custom Behavioral Events API lets product and marketing teams send custom events into HubSpot's behavioral analytics so those events can drive segmentation, automation, and reporting alongside form submissions and page views. The single endpoint accepts a defined event name and per-event property values keyed to a contact. It is the integration point for piping product usage signals — feature_used, plan_upgraded, trial_started — into HubSpot's customer record.

1 endpoints

HubSpot Analytics — Custom Behavioral Events

Jentic publishes the only available OpenAPI specification for HubSpot Analytics — Custom Behavioral Events, keeping it validated and agent-ready. This API is the analytics-side endpoint for landing custom behavioral events against HubSpot contacts so they show up in HubSpot's analytics, lists, and workflows alongside form submissions and page views. The single send endpoint accepts a defined event name, a contact identifier (email, utk, or objectId), and the event's typed property values.

1 endpoints

HubSpot Events API

Jentic publishes the only available OpenAPI specification for the HubSpot Events API, keeping it validated and agent-ready. The Events API exposes the historical CRM object event log — every recorded event tied to contacts, companies, deals, tickets, and custom objects in the portal. Calls return paginated event records filtered by object type, object ID, event type, and time window. It is the read surface for analytics, reporting, and timeline reconstruction across HubSpot CRM data.

1 endpoints

Connect Your Agent

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.