Conversations Inbox & Messages

Name: Conversations Inbox & Messages API
Brand: Conversations Inbox & Messages
Availability: InStock

✓ Official Vendor SpecCommunicationsChat 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.

Quickstart

Get started with Conversations Inbox & Messages in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a reply into a HubSpot conversation thread"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

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

GET STARTED

Start building with Conversations Inbox & Messages API

Explore with Jentic

View OpenAPI Document

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.

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

HubSpot OAuth and private app tokens for the Conversations API are stored encrypted in the Jentic vault. The agent receives a scoped execution token; the raw credential never enters its prompt context.

Intent-based discovery

Agents search Jentic with intents like 'send a HubSpot message' or 'list HubSpot inbox threads' and Jentic returns the right Conversations operation with its input schema, ready to call.

Time to first call

Direct integration including OAuth, pagination, and channel routing typically takes 2-3 days. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot Conversations Custom Channels

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.