Hubspot APIs

93 APIs957 Endpoints12 Categories

API Catalog(7 of 93)

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.

13 endpoints

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.

16 endpoints

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.

12 endpoints

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.

1 endpoints

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.

6 endpoints

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.

3 endpoints

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.

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