Hubspot APIs
93 APIs957 Endpoints12 Categories
Categories
API Catalog(20 of 93)
Authors
The HubSpot CMS Blog Authors API manages the author records that appear as bylines on HubSpot-hosted blog posts. It exposes single and batch endpoints for creating, reading, updating, and archiving authors, plus a multi-language group so the same author can be linked across translated blog content. Use it to keep author profiles, photos, and bios in sync with an external system of record such as a headless CMS or HR directory.
14 endpointsAutomation Actions V4
Define and manage custom workflow actions that extend HubSpot's automation tool with external service integrations. Supports 16 endpoints for creating action definitions, attaching serverless functions to action steps, managing definition revisions, and completing workflow callbacks. Enables developers to build reusable automation actions that HubSpot users can configure within their workflows to call external services, process data, and return results back to the workflow execution context.
16 endpointsAutomation Sequences
The HubSpot Sequences API exposes the sales sequences feature for salespeople doing one-to-one outreach. GET /automation/v4/sequences/ lists the sequences available on the portal, GET /automation/v4/sequences/{sequenceId} returns a single sequence's metadata, GET /automation/v4/sequences/enrollments/contact/{contactId} returns the active enrollment for a specific contact, and POST /automation/v4/sequences/enrollments enrolls a contact in a sequence. Authentication uses OAuth 2.0 access tokens or a private app token sent in the private-app header.
4 endpointsAutomation V4
The HubSpot Automation V4 API gives programmatic access to HubSpot workflows. The /automation/v4/flows endpoints list, create, retrieve, update, and delete workflows, and a batch-read endpoint pulls multiple workflows in a single call. /automation/v4/flows/email-campaigns returns the marketing emails attached to workflows so external systems can audit which sends are workflow-driven, and /automation/v4/workflow-id-mappings/batch/read returns mappings between legacy and migrated workflow ids. Authentication uses legacy OAuth or a legacy private app token in the private-app-legacy header.
8 endpointsBlog Settings
The HubSpot Blog Settings API manages the configuration of each Blog object in a HubSpot portal - the container that holds posts, authors, tags, and templates. It exposes endpoints for reading and updating per-blog settings, listing revision history, and grouping settings across translated blog variants. Use it when the same configuration change must be applied uniformly across multiple blogs or language editions.
9 endpointsCMS Content Audit
The HubSpot CMS Content Audit API exposes a single read endpoint for querying audit logs of CMS changes that occurred on a HubSpot account. It returns who changed what content, when, and from which interface, making it the system of record for compliance reviews and post-incident investigation of CMS edits. The endpoint supports filters for date range, user, and content type so an agent can fetch only the events relevant to a given audit window.
1 endpointsCMS Source Code
The HubSpot CMS Source Code API exposes the file system that backs a HubSpot CMS - templates, modules, stylesheets, and JavaScript that pages and posts render against. It supports reading, writing, validating, and bulk-extracting source files in either the published or draft environments. Use it to manage HubSpot themes from a developer workflow, run validation checks before publishing, or migrate templates between portals.
8 endpointsCommunication Preferences Subscriptions
The HubSpot Communication Preferences Subscriptions API exposes a contact's subscription opt-in and opt-out state across HubSpot subscription types. It supports retrieving a contact's preferences, updating individual subscriptions, unsubscribing from all communications, and running batch reads and writes for many contacts at once. Subscription type definitions can also be listed, making this the right surface for compliance with consent-driven marketing such as GDPR and CAN-SPAM.
9 endpointsDomains
The HubSpot CMS Domains API exposes the domains connected to a HubSpot CMS account. It returns the canonical domain name, the type of content it serves (blog, site pages, landing pages), SSL status, and primary-language flag. Use it when an agent needs to confirm which domain to publish to before creating CMS content, or to audit which domains a portal currently uses for marketing assets.
2 endpointsForms
The HubSpot Forms API manages the lead-capture form definitions that power landing pages, embedded widgets, and pop-up CTAs in a HubSpot account. It supports listing forms, retrieving a form by id, creating new form definitions with field configurations, updating their schema and display configuration, and deleting forms that are no longer in use. Forms created here flow directly into the CMS for embedding and into the Contacts CRM as the lead-capture surface that creates and updates contact records on submission.
6 endpointsMarketing Campaigns Public API
The HubSpot Marketing Campaigns API manages campaigns - the cross-asset organising layer that groups emails, pages, social posts, and ads under a single tracked initiative. It supports listing and reading campaigns, batch creating and updating them, attaching and detaching assets by type and id, recording spend and budget items, and retrieving aggregated reporting metrics on campaign performance. With 24 endpoints across the campaign root, asset, budget, spend, and reporting paths, it gives agents the full lifecycle of a HubSpot campaign object.
24 endpointsMarketing Emails
The HubSpot Marketing Emails API manages the lifecycle of marketing email assets - drafts, AB-test variations, revisions, publishing, and statistics. It supports listing emails, publishing a draft to send, creating and reading AB-test variations, resetting and restoring drafts from prior revisions, and pulling per-email statistics with both list and histogram aggregations. With 19 endpoints across the email, draft, AB-test, revisions, and statistics paths, it gives marketing-ops the editorial workflow plus the reporting layer for outbound email programmes.
19 endpointsMarketing Emails V3
The HubSpot Marketing Emails V3 API is the rollout-155892 build of the marketing email endpoints, covering the same draft, AB-test, revision, publish, and statistics surface but on a newer rollout track. It exposes 17 endpoints for listing emails, reading and resetting drafts, restoring revisions, creating AB-test variations, and pulling per-email statistics as both list and histogram aggregations. Pick this rollout when the consumer needs the latest shape of these endpoints and the matching schema fields.
17 endpointsMarketing Marketing Events
The HubSpot Marketing Events API integrates external event platforms (webinars, conferences, in-person events) with HubSpot so contact attendance and registration become first-class CRM data. It manages marketing event records by externalEventId and externalAccountId, upserts attendance and participation states (registered, attended, cancelled), and exposes participation breakdowns for reporting. With 36 endpoints across event upsert, attendance create, email-create, and participation breakdown paths, it gives event-marketing tools a structured way to push their data into HubSpot timelines and workflows.
36 endpointsMedia Bridge
The HubSpot Media Bridge API lets external media platforms register their video and audio content with HubSpot so it can be embedded, tracked, and reported on alongside other CMS content. It exposes object schemas, custom properties, settings, and event ingestion endpoints - the integrator defines what a media object looks like, registers a connected app, and streams playback events back to HubSpot. The bridge is how third-party media platforms become first-class content in HubSpot reporting.
32 endpointsPages
The HubSpot CMS Pages API manages Site Pages and Landing Pages - the two primary marketing page types in HubSpot's CMS. It exposes endpoints for create, update, batch operations, scheduling, drafting, A/B testing, revisions, and multi-language groupings, plus full folder management for landing pages. Use it to author, schedule, translate, and version marketing pages programmatically rather than through the HubSpot UI.
66 endpointsPosts
The HubSpot CMS Blog Posts API manages every blog post in a HubSpot CMS portal, with single and batch endpoints for create, read, update, archive, schedule, draft, and clone. It includes revision endpoints for restoring or restoring-into-draft, plus a multi-language group so the same post can exist in several locales while sharing one identity. Use it for end-to-end programmatic blog publishing - from drafting to scheduling to archive.
24 endpointsSite Search
The HubSpot CMS Site Search API queries the search index that HubSpot maintains for content hosted on its CMS - site pages, landing pages, blog posts, and knowledge base articles. It exposes a search endpoint that returns ranked results plus an inspector endpoint that returns the indexed payload for a specific content ID, useful for debugging why a page does or does not appear in results. Use it to power on-site search experiences or to programmatically query a portal's public content.
2 endpointsTags
The HubSpot Tags API manages blog tags within the HubSpot CMS, including creation, batch updates, archival, and multi-language tag groupings. It supports attaching tags to language variation groups, designating primary languages, and reading tag metadata for use across HubSpot blog content. Tags are scoped to the HubSpot blog system and link blog posts to topical taxonomies for site search and content organisation.
14 endpointsUrl Redirects
The HubSpot URL Redirects API manages 301 and 302 redirects on HubSpot-hosted CMS sites. It supports listing existing redirects, creating new ones, fetching a redirect by ID, updating destination URLs and precedence, and deleting stale rules. Useful during site migrations, content reorganisation, and SEO maintenance to preserve link equity and avoid broken inbound links.
5 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.