Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Communications / Hubspot / Conversations Inbox & Messages
Conversations Inbox & Messages logo

HubSpot Conversations Inbox & Messages

Browse all Hubspot APIs
41
AI ReadinessFoundational (D-)41/100
See full scorecard
Official vendor OpenAPI document · agent-readyCommunicationsChat Messagingoauth2, apiKey16 EndpointsREST

For Agents

Read HubSpot conversation threads, send messages into existing threads, and manage inbox metadata across email and chat channels. Useful for agents triaging or responding to support conversations.

Use for: List all HubSpot conversation inboxes on this account, Retrieve the message history of a specific support thread, Send a reply into an existing conversation thread, Archive a closed support thread

Not supported: Does not configure custom channels, identify anonymous web visitors, or manage CRM contact records - use for HubSpot inbox thread and message operations only.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Conversations Inbox & Messages to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Conversations Inbox & Messages, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-conversations-inbox-messages" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-conversations-inbox-messages" | 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.

Capabilities

What an agent can do with Conversations Inbox & Messages API.

List conversations inboxes connected to the HubSpot account

Retrieve a thread, its message history, and original message content

Send a reply message into an existing thread

Archive a thread or update its assignee, status, or metadata

List channels and channel accounts available for conversations

Look up actors (users or visitors) associated with messages

Read messages individually or in batches by thread

Use Cases

Patterns agents use Conversations Inbox & Messages API for, with concrete tasks.

★ AI Triage of Support Threads

Pull recent threads from a HubSpot Service Hub inbox, summarise each, and assign them to the right team member or send a templated first response. The Inbox & Messages API exposes thread listings, full message history, and a send-message endpoint, which is the full read-and-respond loop a triage agent needs.

GET /conversations/v3/conversations/threads, then for each unassigned thread GET its messages and POST /conversations/v3/conversations/threads/{threadId}/messages with a triage reply.

Conversation Archival and Audit

Export thread history for compliance or analytics by paging through threads and pulling original message content. The API returns each message's raw content via GET /conversations/v3/conversations/threads/{threadId}/messages/{messageId}/original-content, suitable for archival into a data warehouse.

Iterate threads via GET /conversations/v3/conversations/threads, fetch each thread's messages, and store the original-content payload to S3.

Multi-Channel Reply Bot

Build a reply bot that responds across the channels connected to a HubSpot inbox. The API exposes channels and channel accounts, and POST to a thread's messages endpoint sends a reply on the appropriate channel automatically based on the thread's origin.

On a webhook for a new thread, GET /conversations/v3/conversations/threads/{threadId}, generate a reply, and POST /conversations/v3/conversations/threads/{threadId}/messages.

Agent-Driven Inbox Operations

Wire a HubSpot inbox into an AI agent through Jentic so the agent can read threads, send replies, and archive resolved conversations. Jentic isolates the HubSpot OAuth token from the agent's reasoning context and exposes each operation by intent rather than by URL.

Use Jentic search 'send a reply into a HubSpot conversation thread', load the schema for POST /conversations/v3/conversations/threads/{threadId}/messages, and execute with the threadId and reply text.

Key Endpoints

16 endpoints — the hubspot conversations inbox & messages api exposes the shared inbox model that backs hubspot service hub conversations.

METHOD

PATH

DESCRIPTION

GET

/conversations/v3/conversations/inboxes

List conversations inboxes

GET

/conversations/v3/conversations/threads

List threads

GET

/conversations/v3/conversations/threads/{threadId}

Get a single thread

PATCH

/conversations/v3/conversations/threads/{threadId}

Update a thread

GET

/conversations/v3/conversations/threads/{threadId}/messages

Get message history for a thread

POST

/conversations/v3/conversations/threads/{threadId}/messages

Send a message to a thread

DELETE

/conversations/v3/conversations/threads/{threadId}

Archive a thread

GET

/conversations/v3/conversations/inboxes

List conversations inboxes

GET

/conversations/v3/conversations/threads

List threads

GET

/conversations/v3/conversations/threads/{threadId}

Get a single thread

PATCH

/conversations/v3/conversations/threads/{threadId}

Update a thread

GET

/conversations/v3/conversations/threads/{threadId}/messages

Get message history for a thread

POST

/conversations/v3/conversations/threads/{threadId}/messages

Send a message to a thread

DELETE

/conversations/v3/conversations/threads/{threadId}

Archive a thread

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

C

Conversations Inbox & Messages

- Foundational (D-)
41/100
52
Foundational Compliance
63
Developer Experience & Jentic Compatibility
19
AI-Readiness & Agent Experience
94
Agent Usability
70
Security
63
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
52

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4
89%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

21%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
2%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

19

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
19%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

70

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1
70%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

63

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1
62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring HubSpot Conversations by hand means learning its OAuth2 access token or private app token auth with the conversations scopes, targeting the api.hubapi.com host, and paging inbox threads and messages yourself. Through Jentic you install once, import HubSpot Conversations from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Conversations API puts the thread id in the URL path (/conversations/v3/conversations/threads/{threadId}), so a rule can pin your agent to one thread for reading, updating, and posting messages. You choose the operations it may call, so deleting a thread is not included unless you add it.

Credential isolation

Your HubSpot access token or private app token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a HubSpot message' or 'list HubSpot inbox threads', and Jentic returns the matching Conversations operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot Conversations Custom Channels

→

Register and manage custom channels feeding into HubSpot inboxes.

Pick Conversations-customChannels when the agent needs to wire a non-native channel into HubSpot before reading or replying via the Inbox API.

Complementary

HubSpot Visitor Identification

→

Identify authenticated visitors before they post into a thread.

Use Conversations-visitorIdentification when the agent needs to attach an authenticated identity to chat threads created on the website.

Complementary

HubSpot CRM Contacts

→

Resolve a thread's actor to a CRM contact record.

Choose CRM-contacts when the agent needs full CRM context for the person on the other side of a conversation.

FAQs

Specific to using Conversations Inbox & Messages API through Jentic.

What authentication does the HubSpot Conversations Inbox & Messages API use?

OAuth 2.0 authorization code flow or a private app token in the `private-app-legacy` header. Jentic stores the credential encrypted and exposes only a scoped execution token to the agent.

Can I send a reply into an existing thread with this API?

Yes. POST /conversations/v3/conversations/threads/{threadId}/messages sends a message into the thread, routed automatically through the channel the thread originated on.

What are the rate limits for the Conversations API?

Standard HubSpot API limits apply - roughly 100 requests per 10 seconds per OAuth app and daily caps on paid tiers. For high-volume inbox polling, prefer webhooks and pull thread detail only when an event arrives.

How do I summarise a thread through Jentic?

Search Jentic for `get HubSpot thread messages`, load the schema for GET /conversations/v3/conversations/threads/{threadId}/messages, execute, and feed the message bodies into your LLM. Install with `pip install jentic` and authenticate using `JENTIC_AGENT_API_KEY`.

Does the API expose the original content of an email message in a thread?

Yes. GET /conversations/v3/conversations/threads/{threadId}/messages/{messageId}/original-content returns the raw original message content, useful for archival or for showing full email source to a reviewer.

Can I limit what my agent is allowed to do with the HubSpot Conversations Inbox & Messages API?

Yes. Because you run Jentic One yourself, your own rules decide which Conversations operations the agent may call and which HubSpot credential it uses, so you can allow reading threads and posting a reply while excluding archiving a thread via DELETE /conversations/v3/conversations/threads/{threadId}. Since the thread id sits in the URL path, a rule can also pin the agent to a single thread for getting messages, updating the thread, and sending a reply. The HubSpot token stays with your instance and is added only at execution time, never reaching the agent's prompt or context.

GET STARTED

Start building with Conversations Inbox & Messages API

Explore with Jentic One
View OpenAPI Document