Hubapi APIs
20 APIs151 Endpoints7 Categories
Categories
API Catalog(8 of 20)
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 endpointsCustom 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 endpointsDomains
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 endpointsDomains
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 endpointsMarketing 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 endpointsMarketing 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 endpointsSubscriptions
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 endpointsSubscriptions
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 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.