Manage actorId type to send messages via Conversations API

Developer Support APIs & Integrations
, ,
1

Hello everyone! I was looking to see if anyone had the same problem/doubt as me but I haven’t found anything, if anyone has please let me know.
I am using the Conversations API to send new messages to a thread, I need to add the senderActorId in the RQ body, I get it through the conversations/v3/conversations/threads/{threadId}/messages response. The problem is that the ID is of type visitor and when I try to send the message I get this error: "ActorType `VISITOR` is not supported for `sending`.

In the doc I can see that the Visitor type may not be a contact yet.

Here is my doubt: How can I manage these types of Ids? I mean, right now I have a Contact in HS but my actorId is of type Visitor, is there a simple way to manage this or am I missing something?
Thanks!
Regards.

2

Hello @RaquelRodriguez, thank you for posting in our Community!

I wanted to share this developer doc with more details on Visitor identification that may help you set up this.

I want to invite our top experts to this conversation @skimura @MichaelC @coldrickjack any recommendations for @RaquelRodriguez matter?

Thank you,

Pam

‎

3

I am having the same problem, any solution?

4

@PamCotton Any update on this front? We’re on the enterprise plan, building/integrating/migrating our support system over to Hubspot Tickets/Conversations. But we ran into this complete dealbreaker, which is that only Agents can send messages into a Conversation/Thread/Message. Our customers can not. They are restricted to interacting with the Conversation via email; Why is that?! Our customers won’t be using email, they’ll be filling out an internal form, which we’ll grab and send to HubSpot via the API to submit. But there doesn’t seem to be any way around this. How can we submit a response on behalf of a customer?

Any why can we not “create” a conversation via the API?

5

@PamCotton It seems to have gotten worse in the last couple days; now even Agents can’t send messages into the conversation thread. These are paid HS user accounts…and they can’t send messages to Hubspot?

The exact same POST request I have saved in Postman was working last week, and now it responds with:

subCategory": “ConversationsApiError.UNSUPPORTED_ACTOR_TYPE”,

        "message": "ActorType \`AGENT\` is not supported for \`receiving\`.",

What is the workaround, or will this be fixed? If a (V)isitor, (E)mail, and (A)gent are all unsupported types, how does a conversation on the Conversations API even happen in the first place?

6

We faced the same issue and looks like this is due to an api change. Removing actorId attribute from recepients worked for us.

7

Getting the same error, how did you guys fix this? Also, is the senderActorId the agent or the contact which we’re replying to?

Error response 400 while sending message: {"status":"error","message":"Multiple errors validating request.","correlationId":"eb6ef88d-78a4-466b-b537-52235491f7ba","errors":[{"subCategory":"ConversationsApiError.UNSUPPORTED_ACTOR_TYPE","message":"Actor type VISITOR is not supported for sending","context":{"actorType":["VISITOR"],"operation":["sending"]}},{"subCategory":"ConversationsApiError.INVALID_ARGUMENT_TYPE","message":"Invalid actorId type","context":{"parameter":["actorId"]}}],"category":"VALIDATION_ERROR"}

8

@JAlvarenga2 This was awhile ago that I solved it, so I’d have to pull up the code that handles this and refresh my brain. I seem to remember I had our customer service User talk to a “service account” in order to get the back-and-forth conversation to work with the API constraints. It wasn’t an ideal fix, but it’s worked fine the last couple years and I’ve never had to touch the code again, so that’s nice. I’m happy to have a chat or a screen share if this is still a blocker for you. This was one of my most frustrating API integrations, so I’d love to pass on some knowledge from this process!