Messaging Agent SDK upgrade available
LivePerson empowers external Bot Vendors and Bot Builders to build fully customized bots with LivePerson's Conversational Cloud, leveraging the Messaging Agent SDK for node.js.
We’re excited to share that we have released a new version of NodeAgentSDK which will improve resilience and stability of your third-party bots. Please upgrade to the new NodeAgent SDK as soon as possible to realize these improvements. For the latest SDK version, click here. With the upgrade to the latest version, we recommend auditing your integration to ensure compliance with the best practices around managing connections with LivePerson’s Conversational Cloud. Click here for the best practices.
Messaging/Engagement History API - Adding source name to API calls
As part of our continuous effort to improve troubleshooting and reporting in the historical and operational APIs, we are planning to require a 'source name’ parameter as part of any API calls. This will apply for both internal and external calls.
Why do we require a source name in an API call? Align with API standards, source name is a common practice when building data APIs. Improve monitoring and better control over the traffic. This change will improve the ability to take data-driven actions based on customer source and not by all customer traffic. For example throttling per source. Secure and identify unwanted traffic. Provide more accurate traffic reports to brands.
What are the APIs in scope?
All historial API consumers