Open danishmarif opened 5 years ago
Hi @danishmarif, Yes, our API is accessible directly via WebSockets and is not limited to access through Node.js or this Node Agent SDK.
The SDK provides some conveniences which you will need to address yourself in any other language. If you are familiar with our Chat Agent API, you may be aware of our domain discovery service (CSDS) and login/authentication (agentVep) mechanisms. The SDK handles these things for you. Additionally, it handles the details of creating and managing the WebSocket connection. However, all of this can be done in the language of your choice (any that supports WebSockets).
You can use this SDK as a reference for how to implement each of these things. The initialization is done here: https://github.com/LivePersonInc/node-agent-sdk/blob/master/lib/AgentSDK.js and the WebSocket is handled here: https://github.com/LivePersonInc/node-agent-sdk/blob/master/lib/Transport.js
Due to some backwards-compatibility constraints, there are some differences between this SDK's interfaces and our API itself. Due to this, the easiest way to see the actual requests/responses/notifications is using developer tools to monitor the WebSocket traffic from LiveEngage. Tip: WebSocket connections only show in developer tools if your are already monitoring network traffic when the connection is established.
Is there any way, such as REST Based subscription , or TCP/IP sockets based subscription to interact with the Messaging API of LivePerson , without the need of accessing it only through Node.js ? I went through and tested the Chat Agent API which is REST based and is easily accessible directly from C# / C++ / Postman. So I was wondering if that may be the case with the Messaging API as well.