Problems with using chatParticipant api instead of callParticipant api

Platform API
1

Hello.

Currently, our customer's CRM application is only designed to handle call interactions.
However, while processing Participant events for these call interactions, the application is using the Genesys Chat API (patchConversationsChatParticipant) instead of the Call API (patchConversationsCallParticipant).
However, the application has not experienced any side effects so far.

We need to verify if using the chat API for call interactions could potentially cause any issues.
If anyone could help us with this, it would be greatly appreciated.

2

I doubt anybody is going to guarantee you that using an API for something other than it's intended purpose is going to be risk free.

3

I think so, too.

But the customer's CRM application is using it well,
I wanted to confirm one more time.

Thank you for your answer.

4

I would recommend against knowingly using the wrong endpoint. It may work without issue, but if you do face an issue, the very first troubleshooting step will be to fix the app to use an appropriate endpoint before taking any further steps.

5

I will guide you to modify the customer's CRM application.

Thank you for your answer. tim.smith!

6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.