Hubspot APIs

93 APIs957 Endpoints12 Categories

Categories

All93 Developer Tools6 CRM45 Security1 Identity Auth2 Marketing20 E Commerce3 Payments2 Communications7 Analytics3 Storage1 Productivity2 Finance1

API Catalog

Account Account Info

The HubSpot Account Info API exposes account-level metadata and private app API usage for a HubSpot portal. GET /account-info/v3/details returns the portal id, time zone, currency, company name, and whether the account is sandbox, while GET /account-info/v3/api-usage/daily/private-apps returns the day's call counts for each private app on the portal. The endpoints are designed for ops dashboards and quota monitoring rather than data manipulation. Both calls accept an OAuth 2.0 access token or a private app token in the private-app header.

Account Test Child Api

The HubSpot Account Test Child API is a small surface that returns account-level activity, daily API usage, account details, and security events for a HubSpot portal. The four endpoints under /account-info/v3 are GET-only and read the same portal metadata used by ops dashboards and security tooling. Authentication uses the legacy OAuth scheme or a legacy private app token in the private-app-legacy header. The API is read-only and is intended for monitoring rather than configuration.

Appointments

The HubSpot Appointments API exposes the appointment object inside HubSpot CRM as a generic object resource. It supports listing, creating, updating, archiving, batch operations, and search across appointment records, mirroring the standard HubSpot CRM object shape with custom property maps. Use this API to read or mutate appointment objects programmatically alongside contacts, deals, and other CRM resources.

Audit Logs

The HubSpot Audit Logs API returns user-activity records for a HubSpot portal — successful logins, audit events, and security-history entries such as password changes and two-factor updates. The three endpoints under /account-info/v3/activity each return paginated activity records that a SIEM or compliance dashboard can ingest. The data is read-only and is intended for security monitoring rather than user management. Authentication uses OAuth 2.0 or a private app token.

Auth Oauth

The HubSpot OAuth API covers token introspection and refresh for HubSpot's OAuth 2.0 flow. GET /oauth/v1/access-tokens/{token} returns metadata for an access token including the user, the portal id, and the granted scopes, while GET /oauth/v1/refresh-tokens/{token} returns equivalent metadata for a refresh token. POST /oauth/v1/token completes the standard refresh-token grant to mint a new access token, and DELETE /oauth/v1/refresh-tokens/{token} revokes a refresh token. The endpoints are unauthenticated at the HTTP level because they take the token to inspect or exchange in the path or body.

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.

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

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

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

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

Bucket_Test111

The HubSpot Bucket_Test111 API exposes a custom CRM object type used internally by HubSpot for bucket-style record collections. It provides full CRUD plus search and batch operations against the bucket_test111s object set within the standard CRM v3 object model. Records can be created, archived, merged with other CRM data, and queried alongside contacts, companies, and deals using the same association graph.

Business Units

The HubSpot Business Units API exposes a single endpoint for retrieving the Business Unit records associated with a HubSpot user. Business Units allow multi-brand HubSpot accounts to segment marketing assets, forms, and tracking under separate logos and identities. This API is read-only and is typically used by agents or integrations that need to surface the correct brand context for a given user before performing a downstream action.

Calls

The HubSpot Calls API manages call engagement records in the CRM — the structured log of inbound and outbound calls associated with contacts, companies, and deals. It exposes batch CRUD plus search and upsert against the calls object using the standard CRM v3 object pattern. Each call record can carry properties such as duration, call direction, recording URL, notes, and outcome, and can be associated with other CRM objects.

Carts

The HubSpot Carts API manages cart records inside HubSpot Commerce, representing in-progress purchases that can be associated with contacts, line items, and deals. It exposes the standard CRM v3 object pattern — read, create, update, archive, search, and batch upsert — so cart state from a storefront can be synced into HubSpot for marketing, abandonment workflows, and reporting. Each cart can carry custom properties, line item associations, and currency information.

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

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

Commerce Payments

The HubSpot Commerce Payments API exposes payment records inside HubSpot Commerce, representing captured payments that can be associated with contacts, deals, and invoices. It follows the standard CRM v3 object pattern with batch read, create, update, archive, search, and upsert operations against the commerce_payments object. Records carry properties such as amount, currency, payment method, processor, and reference id, providing a CRM-side ledger that mirrors the payments captured by your processor.

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

Communications

The HubSpot CRM Communications API manages communication engagement records — log entries representing channel-specific messages such as WhatsApp, LinkedIn, or SMS conversations associated with contacts and companies. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, search, and upsert against the communications object. Records carry channel type, body, direction, and timestamp, providing a unified CRM activity timeline for non-email, non-call channels.

Companies

The HubSpot Companies API manages company records — the primary CRM object representing organisations that a HubSpot user does business with. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, search, upsert, and merge operations against the companies object. Each company record carries default properties such as name and domain, supports custom properties, and can be associated with contacts, deals, tickets, and other CRM objects.

Contacts

The HubSpot Contacts API manages contact records — the primary CRM object representing the people a HubSpot user does business with. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, merge, and a GDPR-compliant delete endpoint against the contacts object. Each contact carries default properties such as firstname, lastname, and email, supports custom properties, and can be associated with companies, deals, and tickets.

Conversations Custom Channels

The HubSpot Conversations Custom Channels API lets developers register external messaging surfaces — such as a proprietary chat platform or third-party messenger — as channels inside HubSpot's shared inbox. It supports creating and updating channels and channel accounts, publishing inbound messages, updating message state, and managing channel account staging tokens used for installation flows. With this API a custom channel can behave like native HubSpot conversations channels.

Conversations Inbox & Messages

The HubSpot Conversations Inbox & Messages API exposes the shared inbox model that backs HubSpot Service Hub conversations. It returns inboxes, threads, individual messages, channels, channel accounts, and actor metadata, and allows sending replies, archiving threads, and updating thread state. The API spans the core surface needed to read history and post into existing conversations across email, chat, and connected channels.

Courses

The HubSpot Courses API exposes the Courses CRM object so AI agents can read, create, update, archive, and search course records that sit alongside companies, contacts, and deals. It supports single-record and batch operations through the standard /crm/v3/objects/{objectType} surface, with full support for custom properties and pagination. Courses are commonly used by education, training, and onboarding teams that want learner enrollments tracked inside the same CRM as sales pipeline data.

CRM App Uninstalls

The HubSpot CRM App Uninstalls API provides a single endpoint for triggering an external uninstall of a HubSpot app integration. Calling DELETE /appinstalls/v3/external-install removes the app's installation record for the calling account, useful for offboarding flows and self-service customer-led teardown of an integration. The API is narrow and intended for app lifecycle automation rather than data CRUD.

CRM Associations

The HubSpot CRM Associations v4 API manages links between CRM objects — for example connecting a contact to a deal, a deal to a company, or any object pair allowed by the portal's association schema. It supports single and batch create, read, archive, and label operations, plus default association shortcuts and a high-usage report endpoint. This is the right surface for any workflow that mutates or reads relationships between standard or custom CRM objects.

CRM Associations Schema

The HubSpot CRM Associations Schema v4 API defines and reads the catalog of association types and labels available between CRM object pairs. It supports listing all configured association definitions, reading those for a specific object type pair, and creating, updating, or removing labels and configurations in batch. Use this API to set up the relationship vocabulary that the Associations API then operates on.

CRM Calling Extensions

The HubSpot CRM Calling Extensions API lets calling app developers register and configure their integration so HubSpot users can place and receive calls from inside the CRM. It manages per-app calling settings, recording configuration, channel connections, and notifies HubSpot when call recordings are ready for ingestion. Settings are scoped per HubSpot app id, allowing multi-tenant calling providers to control the experience for each installation.

CRM Contracts

The HubSpot CRM Contracts API exposes a generic CRM object endpoint set parameterised by objectType, providing batch read, create, update, archive, search, and upsert operations against any CRM object collection — including standard objects like companies, contacts, deals, line items, products, tickets, and quotes. Each request takes the objectType as a path parameter and operates on the corresponding object collection using the same v3 patterns. It is the most general-purpose CRM v3 endpoint surface in the HubSpot API.

CRM Crm Owners

The HubSpot CRM Owners API returns the owners that can be assigned to CRM records (contacts, deals, companies, tickets, and custom objects) via the hubspot_owner_id property. It exposes a list endpoint and a single-owner lookup endpoint, both of which include team membership information when teams are enabled on the account. Agents typically call this API to resolve an owner email or ID before creating or updating a record so the new object lands with the correct sales rep or CSM.

CRM Deal Splits

The HubSpot Deal Splits API attributes credit and revenue from a single deal across multiple HubSpot owners so commission and reporting can reflect collaborative selling. It exposes two batch endpoints — read and upsert — that operate on deal-split records keyed off the parent deal ID. This is the API to call when a deal closes and the rep, manager, or specialist all need percentage credit on the opportunity.

CRM Exports

The HubSpot CRM Exports API kicks off asynchronous bulk exports of CRM data — contacts, companies, deals, tickets, custom objects, or saved views — and returns the resulting file as XLSX or CSV. It exposes one endpoint to start an export task and a second to poll its status, which is the right pattern for pulling tens or hundreds of thousands of records without paginating the search API. Exports respect HubSpot property selection and filter criteria, so agents can specify exactly which columns and which records to include.

CRM Imports

The HubSpot CRM Imports API lets you bulk-load CRM records from CSV or spreadsheet files into HubSpot, mapping columns to standard or custom properties on contacts, companies, deals, and other objects. You can start a new import, monitor active imports, cancel an in-progress import, and inspect row-level errors after the job runs. It is the right tool for migrating data from another CRM, syncing periodic exports from external systems, or seeding a HubSpot account with historical records.

CRM Limits Tracking

The HubSpot CRM Limits Tracking API exposes the per-account quota information for the structural pieces of a HubSpot CRM portal — record counts, custom object types, custom properties, calculated properties, pipelines, and association labels. Each endpoint returns a current count, a maximum, and the remaining headroom so an integration or agent can check whether a planned action will exceed the account's plan limits before attempting it. It is the right tool for portal health checks, onboarding readiness validation, and pre-flight checks ahead of bulk imports or schema changes.

CRM Object Library

The HubSpot CRM Object Library API reports which CRM object types are enabled in a given HubSpot portal. It returns the enablement status for every object available in the library, including standard objects (contacts, companies, deals) and HubSpot-shipped specialised objects such as appointments, courses, and listings. Use it as a discovery step before integrating with a portal so the integration knows which objects it can write to and which require enablement first.

CRM Objects

The HubSpot CRM Objects API provides a unified interface for reading, creating, updating, and archiving any standard or custom CRM record by object type. It exposes generic endpoints that operate against companies, contacts, deals, line items, products, tickets, quotes, and any custom object you define on the portal. Batch read, create, update, and archive operations let agents move large volumes of records in a single call, and a search endpoint supports filtering and pagination across object types. Use it as the primary CRUD layer when you need a single integration that works across HubSpot's full object model rather than a separate client for each record type.

CRM Pipelines

The HubSpot CRM Pipelines API manages the pipelines and pipeline stages that define how records move through a workflow — sales deals through sales stages, support tickets through resolution stages, and any custom-object pipeline a portal defines. Endpoints cover full CRUD on pipelines and stages, plus dedicated audit endpoints that return the change history for both. Agents can list, read, create, update, and delete pipelines for a given object type, manage the ordered list of stages within each pipeline, and inspect every change made to either through the audit log. Use it to provision pipelines for a new portal, programmatically rename stages without breaking automation, or build governance dashboards from the audit history.

CRM Property Validations

The HubSpot CRM Property Validations API reads the validation rules HubSpot enforces on the properties of a CRM object — pattern checks, length constraints, enumerated value lists, and other input rules. It exposes a single object-type-level endpoint that returns every validation rule for the object's properties, plus a property-level endpoint that returns the rule for one named property. Use it to mirror HubSpot's validation logic in an external form, prevent failed writes by validating input client-side before calling the CRM Objects API, and document the input contract for downstream agents.

Deals

The HubSpot Deals API manages the deal records that drive HubSpot sales pipelines, exposing single and batch CRUD plus search across the standard /crm/v3/objects/deals surface. It supports pipeline stage transitions, deal property updates, deal merging, and association lookups so agents can move opportunities through pipelines programmatically. This is the primary API for any AI agent that needs to read, update, or report on revenue-stage data inside HubSpot.

Discounts

The HubSpot Discounts API manages discount records that can be applied to HubSpot quotes and line items, exposing single and batch CRUD plus search across /crm/v3/objects/discounts. It supports percentage and fixed-amount discounts, custom properties, and standard pagination so agents can read, create, and reconcile discount catalogues programmatically. Use it whenever quote pricing depends on reusable discount records rather than ad-hoc line-item adjustments.

Domains

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.

Emails

The HubSpot Emails CRM API manages email engagement records — logged emails, replies, and email metadata — that appear on contact and deal timelines. It exposes single and batch CRUD plus search across /crm/v3/objects/emails, supporting custom properties, pagination, and association lookups. Use it to log outbound emails sent from external tools, sync inbox replies, or pull engagement history for reporting; it does not send marketing or transactional emails.

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.

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

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

Feedback Submissions

The HubSpot Feedback Submissions API exposes feedback submission records — typically NPS, CSAT, and CES survey responses captured by HubSpot's feedback tool — as a CRM object so AI agents can read and search them alongside contacts and deals. It exposes a list endpoint, a single-record retrieve, a batch read, and a search endpoint, all read-oriented because feedback submissions are created by HubSpot when a survey response arrives. Use it to pipe customer sentiment into reporting, route detractors, or correlate scores with deal outcomes.

Fees

The HubSpot Fees API manages fee records used on quotes and line items, exposing single and batch CRUD plus search across /crm/v3/objects/fees. Fees represent shipping, handling, processing, or service charges that are added to a customer-facing quote alongside the product line items. Agents use this API to maintain a reusable fee catalogue, attach fees to quotes, and reconcile billed fees in commission or revenue reporting.

Files

The HubSpot Files API uploads and manages files in the HubSpot file manager — the storage layer behind email images, CMS pages, knowledge base attachments, and CRM record uploads. It supports direct multipart uploads, asynchronous import-from-URL for large external files, folder organisation, and signed-URL generation for private file access. Files can be checked for duplicates by stat path, retrieved by id, GDPR-deleted, and listed by folder, giving agents full control over the asset library that other HubSpot APIs reference by file id.

Forms

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.

Goal Targets

The HubSpot Goal Targets API manages goal target records — the per-rep, per-team, or per-period targets that drive HubSpot's goals reporting (revenue goals, activity goals, deal-count goals). It exposes single and batch CRUD plus search across /crm/v3/objects/goal_targets, with custom property support so agents can program quota cycles, adjust targets mid-period, and reconcile actuals against plan. Use it to automate quarterly target rollouts, mid-cycle adjustments, and goal reporting pulls.

HubSpot CRM Custom Objects

Jentic publishes the only available OpenAPI specification for HubSpot CRM Custom Objects, keeping it validated and agent-ready. Define and operate on bespoke CRM object types that extend HubSpot beyond standard contacts, companies, deals, and tickets. Store industry-specific records — such as vehicles, properties, or subscriptions — with full association, search, batch, and merge support across the HubSpot CRM graph. Requires an Enterprise-tier HubSpot account.

HubSpot CRM Schemas

The HubSpot CRM Schemas API defines how custom objects store and represent information in the HubSpot CRM. A schema describes an object type's properties, primary display property, secondary display properties, searchable properties, required fields, and supported associations to other CRM objects. The API exposes operations to list all schemas, create a new schema for a custom object, fetch or update an existing schema by objectType, delete a schema, and add or remove associations between schemas — making it the foundation for any HubSpot integration that goes beyond the standard contact, company, deal, ticket, and quote objects.

HubSpot Meetings

The HubSpot Meetings API exposes the public-facing meeting links that sales reps and customer success managers publish through the HubSpot Sales scheduler. Through it an integration can list every published meeting link on a HubSpot account, fetch the rendered availability page for a specific link, and book a slot programmatically on behalf of a contact. It is the same booking surface that powers the HubSpot meeting widget on customer-facing sites.

HubSpot Multicurrency

The HubSpot Multicurrency API manages the currency configuration that every deal, quote, and revenue report on a HubSpot portal depends on. It exposes the company's home currency, the supported ISO currency code list, and the active and historical exchange rates used to convert deal amounts back to the home currency. Rates can be created, batch updated, hidden from the UI, and queried by ID so finance teams can keep HubSpot's reporting aligned with their accounting source of truth.

HubSpot User Provisioning

The HubSpot User Provisioning API manages the user directory of a HubSpot account: who has a seat, what role they hold, and which team they belong to. It supports inviting and removing users, fetching the role and team rosters, and updating an individual user's role assignment. Identity providers and HRIS systems use it to keep HubSpot's seat allocation in sync as people join, change teams, or leave the company.

HubSpot Webhooks

The HubSpot Webhooks API configures the change-event subscriptions that a HubSpot app pushes to a target URL. It manages the app-level webhook settings such as target URL and throttling, and the per-event subscriptions for specific objects and event types. Subscriptions can be created, paused, batch updated, and deleted so apps stay aligned with the HubSpot data they need to react to in near real time.

Invoices

The HubSpot CRM Invoices API exposes the invoice object that sits alongside deals, line items, and quotes in HubSpot Commerce. Agents and integrations can create, read, update, archive, search, and batch-process invoice records, and associate invoices with the contacts, companies, deals, and line items they belong to. It is intended for synchronising invoice data between HubSpot and external billing systems and for building invoice-aware sales workflows inside HubSpot.

Leads

The HubSpot CRM Leads API exposes the lead object that sits between contacts and deals in the HubSpot Sales Hub prospecting workspace. It supports create, read, update, archive, batch operations, and property-filtered search for lead records, allowing integrations to push prospect data into the prospecting queue and update qualification status as agents or reps progress them. It is the right entry point for connecting a SDR tool, lead-routing engine, or scoring model to HubSpot's prospecting workflow.

Line Items

The HubSpot CRM Line Items API manages the priced rows that compose deals, quotes, invoices, and subscriptions in HubSpot Commerce. It exposes single-record CRUD, batch read, batch create, batch update, batch upsert, batch archive, and search for line item records with full property and association support. Use it to build a quote out of products, attach line items to a deal during pipeline progression, or sync line-level pricing data between HubSpot and an external billing or e-commerce system.

Listings

The HubSpot CRM Listings API provides a generic, object-type-parameterised CRUD and search interface for any standard or custom object in the portal. Endpoints accept an objectType path parameter so the same operations work for contacts, companies, deals, line items, products, tickets, quotes, listings, and any custom object schema the portal has defined. Use it when an integration or agent needs to operate over many object types from a single set of operations rather than wiring per-object endpoints.

Lists

The HubSpot CRM Lists API manages static and active (filter-defined) lists for any CRM object — contacts, companies, deals, custom objects. It supports list creation, deletion, renaming, filter-definition updates, membership add and remove, search across lists, folder organisation, and translation between legacy and modern list IDs. Use it to build segmentation logic, drive marketing or workflow membership, or programmatically curate audiences for downstream automation.

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

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

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

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

Marketing Single-send

The HubSpot Marketing Single-send API delivers a one-off send of an existing marketing email to a single recipient with custom contact properties and personalisation tokens applied at send time. It exposes a single POST endpoint that takes the emailId, recipient, and custom property overrides, returning a send status the caller can log and retry on. Useful for transactional-style triggers where you want HubSpot's marketing email template engine and tracking but without enrolling the contact in a list-based send.

Marketing Transactional Single Send

The HubSpot Marketing Transactional Single Send API delivers one-off transactional emails such as receipts, password resets, and account notifications using a HubSpot-designed email template. Senders authenticate either with OAuth or with HubSpot SMTP API tokens that can be created, fetched, and rotated through the same API. The API tracks each send against the standard HubSpot marketing email engagement reporting so transactional opens, clicks, and bounces appear alongside other email activity.

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

Meetings

The HubSpot CRM Meetings API manages the meeting engagement object that records calendar interactions between reps and contacts in the HubSpot CRM. It supports single-record CRUD, batch read, batch create, batch update, batch upsert, batch archive, and search across meeting properties and associations. Use it to log meetings from an external calendar, sync meeting outcomes back into HubSpot, or surface meeting history on a contact or deal timeline.

Notes

The HubSpot CRM Notes API manages the note engagement object that captures free-text annotations on contacts, companies, deals, and tickets in HubSpot. It supports single-record CRUD, batch read, batch create, batch update, batch upsert, batch archive, and search across note properties and associations. Use it to log AI-generated meeting summaries, sync notes from a sales engagement tool, or surface annotation history on a contact timeline.

Orders

The HubSpot CRM Orders API exposes order records inside the HubSpot CRM as a first-class object with read, list, search, and patch operations. It supports batch read, create, update, and archive of up to 100 orders per call, and a search endpoint that can filter by any order property. Use it to sync external commerce orders into HubSpot for reporting, to associate orders with contacts, deals, or line items, or to drive marketing and sales workflows from order events. The endpoints follow the same generic CRM object pattern as other HubSpot CRM resources, so agents that already know how to call /crm/v3/objects/{objectType} can drop in immediately.

Pages

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.

Partner Clients

The HubSpot Partner Clients API exposes the partner_clients CRM object that HubSpot Solutions Partners use to track the customer accounts they have referred or are managing. It supports reading individual partner client records, listing partner clients with pagination, batch read and batch update of up to 100 records per call, and a search endpoint for filtering by property. The API does not expose create or archive operations because partner client records are provisioned through HubSpot's partner enrollment flow rather than directly via the API. Use it to audit your partner book of business, sync partner client metadata into a partner portal, or drive reporting on referred accounts.

Payments

The HubSpot CRM Payments API exposes payment records as a CRM object so agents can read, list, batch-read, and search the payments stored against a HubSpot portal. Each payment record represents a financial transaction associated with a contact, deal, or order in the CRM and includes properties such as gross amount, currency, status, and creation date. The API is read-only — payment records themselves are produced by HubSpot's commerce flows or by the Commerce Payments API rather than created here. Use it for reporting on settled payments, reconciling CRM data with an upstream commerce system, and exposing payment history to sales workflows.

Postal Mail

The HubSpot Postal Mail API treats postal mail engagements — direct mail letters, postcards, packages — as first-class CRM records that can be logged against contacts, companies, and deals. It supports the standard CRM object pattern: read, list, patch, and archive single records, plus batch read, create, update, and archive of up to 100 records per call, and a search endpoint with filter groups and sort. Use it to log direct mail sends from a print partner back into the CRM, build outreach reports that combine digital and offline channels, and trigger follow-up sequences once a piece of postal mail is delivered.

Posts

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.

Products

The HubSpot CRM Products API manages the product catalogue inside a HubSpot portal — the master list of products that quotes, deals, and orders reference through line items. It supports the full CRM object pattern: read, list, patch, and archive single products, plus batch read, create, update, and archive of up to 100 products per call, and a search endpoint with filter groups and sort. Use it to seed a HubSpot portal from an external product database, keep prices and SKUs in sync with an upstream system of record, and build product pickers inside sales tools that talk straight to the live catalogue.

Properties

The HubSpot CRM Properties API manages the schema layer that sits behind every CRM object — the named fields stored on contacts, companies, deals, tickets, and custom objects. It exposes endpoints to create, read, update, and archive properties for any object type, organise them into property groups, and run batch read or archive operations. Use it to bootstrap the custom fields a portal needs, keep the field schema in sync with another system of record, document the field model for compliance reviews, and clean up unused properties after a redesign. Read access works without write scopes, so agents that only need to introspect the schema can stay scoped down.

Public App Crm Cards

The HubSpot Public App CRM Cards API lets a public HubSpot app declare and manage the custom cards it surfaces in the sidebar of CRM record pages. Each card is registered up-front against an app ID with a target object type, a fetch URL HubSpot calls when a record is opened, and a definition of the actions and properties to render. Endpoints cover create, read, update, and delete of cards under a given app, plus a sample response endpoint that returns a representative payload so app developers can build a matching fetch handler. Use it to build product integrations that show external data — open invoices, ticket counts, account health — directly inside the HubSpot CRM UI.

Public App Feature Flags V3

The HubSpot Public App Feature Flags V3 API lets developers of HubSpot public apps roll out features gradually by toggling per-account flag states. Developers define a feature flag at the app level and then enable, disable, or query the flag state for individual HubSpot portals (accounts) using the app. The API supports single-portal updates, batch upserts, batch deletes, and lookups across all portals where a flag has been set, making it suitable for staged rollouts, A/B experiments, and emergency feature kill switches.

Quotes

The HubSpot CRM Quotes API lets sales teams and integrations programmatically create, read, update, archive, and search Quote records — the documents that capture proposed pricing, terms, and line items presented to a buyer. Each quote is a CRM object that can be associated with deals, contacts, companies, line items, and signatures, and supports custom properties just like other HubSpot CRM objects. The API exposes single-record CRUD, batch create, batch read, batch update, batch upsert, batch archive, and a search endpoint with filtering and sorting.

Services

The HubSpot CRM Services API provides a generic CRUD, batch, and search interface over any HubSpot CRM object type — including standard objects (companies, contacts, deals, line items, products, tickets, quotes) and custom objects defined via the Schemas API. Endpoints are templated on /crm/v3/objects/{objectType} so a single integration pattern works for every object type in the portal. The API supports single-record operations (read, update, archive), batch read, batch create, batch update, batch upsert by unique property, batch archive, and a full-featured search with filters, sorting, and paging.

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

Subscriptions

The HubSpot Commerce Subscriptions API manages subscription records inside HubSpot Commerce — the CRM-side representation of a recurring billing relationship between a contact and a product. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, search, and upsert against the subscriptions object. Each subscription can carry properties such as billing cycle, next renewal date, status, and associated contact, deal, and line items, mirroring an external billing system into the CRM.

Tags

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.

Tasks

The HubSpot CRM Tasks API manages Task records — to-dos that sales reps and CSMs use to follow up with contacts, deals, and tickets in HubSpot. Tasks have due dates, owners, statuses, types (call, email, to-do), and priorities, and can be associated with any other CRM object. The API exposes single-record CRUD, batch read, batch create, batch update, batch upsert by unique property, batch archive, and a full search endpoint with filters on owner, due date, status, and any custom property.

Taxes

The HubSpot CRM Taxes API manages Tax records — the named tax rates that HubSpot Commerce applies to line items on quotes, invoices, and subscriptions. Each Tax record has a label, rate, and optional jurisdiction metadata, and can be associated with the line items it applies to. The API exposes single-record CRUD, batch read, batch create, batch update, batch upsert by unique property, batch archive, and a search endpoint with filters and sorting.

Tickets

The HubSpot CRM Tickets API manages support ticket records — the customer issues that flow through HubSpot Service Hub pipelines. Tickets have status, priority, owner, source, and category properties, and can be associated with contacts, companies, deals, conversations, and any custom CRM object. The API exposes single-record CRUD, batch read, batch create, batch update, batch upsert by unique property, batch archive, ticket merge, and a search endpoint with full filter, sort, and paging support.

Timeline

The HubSpot CRM Timeline API lets a public app create custom timeline events that appear on the timeline of CRM records — contacts, companies, tickets, and deals. Apps first define event templates that describe the event type, header, detail, and tokens (event-specific fields), then emit individual events that bind values to those tokens. The API supports template management (create, list, get, update, delete event templates), token management on a template, single and batch event creation, and rendering of an event's header and detail as HTML for display inside HubSpot.

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

Users

The HubSpot CRM Users API exposes the User CRM object, which represents end users tracked alongside contacts, companies, and deals (distinct from the HubSpot account owners managed by the Users Provisioning API). Each User record supports custom properties, associations to other CRM objects, and the standard CRM object operations. The API includes single-record CRUD, batch read, batch create, batch update, batch upsert by unique property, batch archive, and a search endpoint with filters and sorting on /crm/v3/objects/users.

Video Conferencing Extension

The HubSpot CRM Video Conferencing Extension API lets a public app register the URLs HubSpot uses to manage video conferencing on meeting requests with contacts. The app provides three URLs — create, update, and delete — that HubSpot calls when a meeting link needs to be generated, modified, or removed for a HubSpot meeting. Once configured, HubSpot adds the resulting video conference link to the meeting invitation automatically. The API exposes three endpoints to get, update, and delete the extension settings for a given appId.

Visitor Identification

The HubSpot Visitor Identification API issues short-lived identification tokens that pass authenticated visitor identity into the HubSpot chat widget. It accepts an email and friendly name from your own authentication system, and returns a token that the HubSpot chat widget consumes so the chat session is associated with a known contact rather than an anonymous visitor. This is the primary surface for identified-visitor chat experiences on HubSpot-hosted and embedded chat widgets.

Connect 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 | sh

2

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.