Hubspot APIs
93 APIs957 Endpoints12 Categories
Categories
API Catalog(3 of 93)
Events Events
The HubSpot Events API exposes behavioural event streams captured against contacts in a HubSpot account, returning the chronological list of events with type, occurrence time, and contact context. It supports filtering by event type, object id, and time window so analytics agents can reconstruct customer journeys without scraping the CRM UI. The companion event-types endpoint enumerates which event names are available in the portal, including standard events (page views, form submissions, email opens) and custom behavioural events defined by the account.
2 endpointsEvents Manage Event Definitions
The HubSpot Manage Event Definitions API lets you create, update, and delete the schemas for custom behavioural events tracked against contacts in a HubSpot account. Each event definition declares a unique event name and a set of typed properties, which then governs every occurrence sent through the Send Event Completions API. This API also supports adding, updating, and removing individual properties on an existing event definition without redefining the whole schema, which keeps custom events evolvable as the product or campaign tracking changes.
8 endpointsEvents Send Event Completions
The HubSpot Send Event Completions API records occurrences of custom behavioural events against contacts in a HubSpot account. A single send endpoint posts one event with its eventName, contact identifiers (utk, email, or objectId), occurrence time, and property values, while a batch endpoint sends up to 100 occurrences in one call. Once recorded, occurrences flow into the same event store that powers HubSpot reporting, contact timelines, and workflow triggers — closing the loop between product behaviour and CRM segmentation.
2 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.