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 endpointsThe 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 endpoints# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.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.