Hubapi APIs

20 APIs151 Endpoints7 Categories

API Catalog

CRM cards

Jentic publishes the only available OpenAPI specification for CRM cards, keeping it validated and agent-ready. The HubSpot CRM cards API lets developer apps extend the CRM record sidebar by registering custom cards that pull data from external systems when a user opens a contact, company, or deal record. Cards are configured up-front per app and populated at view time by an external data fetch URL the app exposes. This is the building block for embedding third-party context — order history, support tickets, billing — directly in the HubSpot CRM UI.

6 endpoints

CRM cards

Jentic publishes the only available OpenAPI specification for HubSpot CRM Cards, keeping it validated and agent-ready. The CRM Cards API lets a HubSpot app extend the CRM UI by surfacing custom cards in the sidebar of contact, company, deal, and ticket record pages. Apps register card definitions up front, including the data fetch URL HubSpot calls when a record loads. The card definitions, sample-response shape, and per-app card list are all managed through this API.

6 endpoints

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

Custom Workflow Actions

Jentic publishes the only available OpenAPI specification for Custom Workflow Actions, keeping it validated and agent-ready. HubSpot Custom Workflow Actions let app developers register their own action blocks that appear in the HubSpot workflow builder, so customers can drop a third-party step (send a message, create an order, run a calculation) into a marketing or operations workflow. The API covers action definitions, function code attached to each action, callbacks for long-running steps, and revision history for safe rollouts.

16 endpoints

Custom Workflow Actions

Jentic publishes the only available OpenAPI specification for Custom Workflow Actions, keeping it validated and agent-ready. The HubSpot Custom Workflow Actions API lets developers extend HubSpot workflows with custom action definitions that are invoked from automation flows. Apps can register action definitions, manage revisions, define input fields, and respond to callback executions. It is designed for ISVs building extensions that participate in HubSpot's marketing, sales, and service automation engine.

16 endpoints

Domains

Jentic publishes the only available OpenAPI specification for HubSpot CMS Domains, keeping it validated and agent-ready. The HubSpot CMS Domains API exposes the connected domains attached to a HubSpot CMS portal — including primary, secondary, and HubSpot-hosted preview domains. It returns metadata such as the domain name, whether SSL is provisioned, and which content type (site, blog, landing pages) the domain is mapped to. It is the read surface for understanding which sites a HubSpot portal currently publishes to.

2 endpoints

Domains

Jentic publishes the only available OpenAPI specification for HubSpot CMS Domains, keeping it validated and agent-ready. The HubSpot CMS Domains API exposes the connected domains attached to a HubSpot CMS account — the hostnames used to serve websites, blogs, and landing pages. Agents and integrations can list every domain configured in the portal and read individual domain records by ID. It is the read surface that powers content publishing decisions in HubSpot's CMS Hub.

2 endpoints

Files

Jentic publishes the only available OpenAPI specification for HubSpot Files, keeping it validated and agent-ready. The HubSpot Files API manages the file manager attached to a HubSpot portal — uploading binary files, importing from URLs, organising them into folders, generating signed URLs for private files, and handling GDPR deletion. Files stored here are referenced by HubSpot CMS pages, marketing emails, and CRM records, so the API is the integration surface whenever an agent or app needs to put assets into the HubSpot ecosystem.

18 endpoints

Files

Jentic publishes the only available OpenAPI specification for HubSpot Files, keeping it validated and agent-ready. The HubSpot Files API uploads, organises, and serves files used across the HubSpot platform — images embedded in marketing emails, PDFs attached to deals, documents shared in conversations. It supports direct upload, async import-from-URL, signed URL generation, folder management, and GDPR delete. Files and folders can be searched by name, parent path, and access level.

18 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

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 endpoints

Marketing Events Extension

Jentic publishes the only available OpenAPI specification for the HubSpot Marketing Events Extension, keeping it validated and agent-ready. The Marketing Events Extension API registers external marketing events — webinars, conferences, virtual sessions — inside HubSpot so contact attendance and registration are visible alongside other CRM activity. Apps create or upsert events by externalEventId, search and cancel events, and record per-attendee state transitions like REGISTERED, ATTENDED, or CANCELLED. It bridges third-party event platforms (Zoom, On24, Eventbrite) with HubSpot's marketing record.

16 endpoints

Marketing Events Extension

Jentic publishes the only available OpenAPI specification for the Marketing Events Extension, keeping it validated and agent-ready. The Marketing Events Extension API registers external marketing events such as webinars, conferences, and virtual sessions inside HubSpot. Apps create or upsert events keyed by externalEventId, search and cancel events, and record per-attendee state transitions like REGISTERED, ATTENDED, or CANCELLED. The same surface configures app-level integration settings and delivers attendance updates by either contactId or email.

16 endpoints

Subscriptions

Jentic publishes the only available OpenAPI specification for HubSpot Subscriptions, keeping it validated and agent-ready. The HubSpot Communication Preferences API manages subscription types — the topics or brands that contacts can opt into or out of for marketing communications. It returns the subscription definitions for a portal, reads the current opt status for an email address, and applies subscribe or unsubscribe changes. It is the compliance-critical surface for honouring contact consent.

4 endpoints

Subscriptions

Jentic publishes the only available OpenAPI specification for Subscriptions, keeping it validated and agent-ready. The HubSpot Subscriptions API lets contacts control which forms of communication they receive from a HubSpot account, scoped to specific topics, brands, or the whole portal. Agents can list subscription definitions, read a contact's subscription status by email, and subscribe or unsubscribe contacts to keep marketing consent state in sync with external preference centres. The four endpoints under /communication-preferences/v3 cover the full read and update flow for contact-level consent.

4 endpoints

Visitor Identification

Jentic publishes the only available OpenAPI specification for HubSpot Visitor Identification, keeping it validated and agent-ready. The Visitor Identification API issues identification tokens that pass authenticated visitor information to the HubSpot chat widget. When a visitor is signed in to your own application, you can vouch for their identity and the chat widget will associate the conversation with the matching HubSpot contact instead of treating them as anonymous. It is the bridge between your app's auth system and HubSpot's live chat surface.

1 endpoints

Visitor 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 endpoints

Webhooks API

Jentic publishes the only available OpenAPI specification for the HubSpot Webhooks API, keeping it validated and agent-ready. The Webhooks API lets a HubSpot app subscribe to change events on contacts, companies, deals, tickets, and other CRM objects. It manages subscription rules per app and configures the target URL HubSpot calls when matching events occur. Settings, individual subscriptions, and batch subscription updates are all managed through this surface.

9 endpoints

Webhooks API

Jentic publishes the only available OpenAPI specification for Webhooks API, keeping it validated and agent-ready. The HubSpot Webhooks API lets a HubSpot public app subscribe to change events on contacts, companies, deals, tickets, and other CRM objects, then receive event payloads at a single configured target URL. Apps can configure a target URL with a max-concurrent-requests cap, then create, list, update, or archive subscriptions to specific event types. Authentication uses the developer-account hapikey because subscription configuration is scoped to the developer's app, not an end customer portal.

9 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.