We have made an Open Message integration and using the following API successfully for sending Inbound messages,
POST /api/v2/conversations/messages/inbound/open.
Now, we need an API to send messages in the vice versa direction.
I didn't see any such API, however in the same API above there is a parameter called as "direction" with valid values of "Inbound" and "Outbound".
I am trying this API request with "direction":"Outbound" value and getting 200 OK result.
But no message is showed in the conversation.
Does this API works with "direction":"Outbound" parameter for the purpose of sending outbound message?
If it is possible, what must be the "from" and "to" parameters in the request, can you please write an example request.
hi @ugur.bayramoglu your inbound open message gets the message into Genesys Cloud from your service. Once the message is in Genesys Cloud, there is now a Genesys Conversation associated with it. Typically it's routed to a bot or queue/agent, but really depends on what you want there. Your Architect Flow that is setup on that Open Integration you created, decides what to do with the inbound message and routing. About open messaging - Genesys Cloud Resource Center see the Message and in-queue flow routing section on this page for more info
For instance if your message was routed to an Agent then the agent would send replies back outbound using post-api-v2-conversations-messages--conversationId--communications--communicationId--messages for instance. You can find many other /api/v2/conversations/messages/* api endpoints to do various other things with the conversation as well.
Actually we are using a 3rd party chatbot and didn't integrate it with genesys cloud since architect message flows don't support asynchronous message sending whenever our Bot sends an outbound message even the customer does not write something.
However, we are using cloud services for the agent messaging and agent must see all the conversation history made by 3rd party bot.
So we have found a workaround to save every copy of the message between Bot and the User by calling this Inbound message API.
But, we need to save the messages on behalf of a virtual agent as well in to the conversation.
This purpose is our requirement to send outbound message API before transferring to an agent.
This is not the intention of this API. I don't think I understand your use case specifically. But to answer your original question, no you cannot use the POST /api/v2/conversations/messages/inbound/open. to outbound a message to your open integration webhook. The Genesys /api/v2/conversations/messages/* apis I mentioned before, are for the outbound messages there.