Schema issues for /api/v2/conversations/messages/{integrationid}/inbound/open/message"

[alex7]

I'm seeing this error coming back from Genesys when I call this API:

"message": " should have required property 'content', should have required property '.text', should match some schema in anyOf"

The payload is this:
{
"channel": {
"from": {
"id": "jack@black.com",
"nickname": "Jabroni",
"idType": "Email",
"firstName": "Jack",
"lastName": "Black",
"email": "jack@black.com"
},
"time": "2024-10-31T19:43:10.286024Z",
"messageId": "abc123"
},
"metadata": {
"BU": "BCC"
}
}

According to API Explorer, "content" is not required. I'm not exactly sure about ".text" either. "text" isn't required either.

Where can I see the schema?

[Greg_Boston]

The issue here is that you aren't giving any text/content for the message. So it's failing due to that. There is nothing to route/handle with blank messages. Neither text or content field is required on it's own (because you don't have to have both of them in each request), but you would have to have 1 or the other to get the message to inbound. I'm not sure if you've reviewed some of the docs on open messaging yet, but I would start there inboundTextMessages

[alex7]

Yes. I was about to respond to my own post that I figured it out. I found some sample messages (from that same link you provided) and got it to work.

I'm trying to integrate a 3rd party chat service with Genesys so the customer can be routed to an agent if necessary. I thought I could use Open Messaging and the empty inbound text was for the initial route request.

Is using Open Messaging the way to do it?

[Greg_Boston]

It sounds like you want something like this webmessaging/websocketapi#customer-join which is supported in webmessaging today, but not open, yet. Doesn't mean it won't be added to open eventually, but I can't give you any concrete timelines there. You could try to use webmessaging for your use case possibly.