Create an email conversation thread on a ticket via API, so the customer's reply lands back on that

We create support tickets automatically from inbound phone calls, so those tickets have no conversation thread. We want to email the customer our answer from our shared support inbox and have their reply come back onto the same ticket. A human does this in seconds from the Help Desk. We cannot find any supported way to do it from the API.

What we tried, with the actual results

- POST to the conversations threads collection returns 405, while GET on the same collection returns 200. The v4 equivalent is 404.

- Replying into an existing thread works: POST /conversations/v3/conversations/threads/{threadId}/messages returns 400 VALIDATION_ERROR rather than 404, so only thread creation is missing.

- PUT /crm/v4/objects/ticket/{ticketId}/associations/default/conversation/{threadId} returns 200 and attaches an existing thread to a threadless ticket, so association is not the problem.

- The Help Desk UI uses a private front end RPC, createEmailThreadAndSend, which is cookie and CSRF authenticated and not usable with a private app token.

- Single send needs the transactional email add on, and creates no thread anyway.

- The only email action a ticket workflow offers points at a marketing asset, which is not our shared inbox and creates no thread.

- An email engagement created with hs_email_status: SENT logs on the timeline and delivers nothing.

Question

Is there any supported route today, public or beta, for an app to originate an email thread on a ticket in a shared inbox?

This has been asked before without resolution

- I create a Ticket via API - It's got no Conversation (Feb 2026, accepted answer says no public API can create a thread)

- Idea, still open since Aug 2023: Create Conversation over the API

Hey @Nicolas5,

Welcome to the Community and thanks for the detailed post!! :raising_hands:

Thanks for noting th existing threads. The Conversations API docs only cover reading threads and sending to existing ones. Seeing that one of the threads you’ve linked is a Feature Request that isn’t marked as delivered, I believe this may still be a limitation. That said, tagging in some folks from the Community to see if they’ve worked around this:

Hey @Alex_Boissonneault, @JasmineOejbro, @remingtonbegg have you ever come across this behavior before?

Sam, Community Manager

@Nicolas5 I’ve hit this wall before. From what I can see in HubSpot’s developer docs, the Conversations API lets you read, update and archive threads, and post messages to a thread that already exists. I couldn’t find an endpoint that creates a thread, so I wouldn’t build on the private front-end call. It isn’t supported and could break any time.

What I’d try instead:

  • Have a person open the ticket in Service, Help Desk and send the first email from the reply editor. That creates the thread, and the customer’s reply lands on it.
  • Make sure the ticket has a contact associated first. The reply editor only shows up after that.
  • Once the thread exists, use the API to post follow-up messages or internal comments to it.
  • Find it by filtering threads on associatedTicketId.
  • Ask HubSpot Support too, in case a beta route exists that the docs don’t show.

Help Desk needs Service Hub Professional or Enterprise. Let me know if you want help setting up the hand-off.

Help article (has screenshots): Create and respond to tickets in help desk