Most user actions within LiveEngage can be performed programmatically using the REST API. Since we use a REST model, we recommend you be fluent in:

  • JavaScript, and its iterations like Node.JS, as well as JSON. Although most JSON payloads tend to be simple, there are exceptions to this rule, like with Structured Content.
  • Swift and Java, respectively, for Mobile App Messaging SDKs for iOS and Android.
  • HTTP calls and responses, REST APIs, server to server communication and web applications.
  • Retrieving information and data analysis/research for the Data APIs.

Also, if you have not already done so:

  1. Read the API Terms of Use.
  2. Read the Systems Requirements and Language Support guide.

And before you can do anything, you must do a few things first. By the end of this Getting Started guide, you will be ready to customize and implement features in LiveEngage.



Step 1. Create a LiveEngage account

Before you can use LiveEngage, you must first have a working account. If you don't already have one, you can sign up for a free trial account. to get started with messaging, Conversation Builder, and LivePerson Functions. To add more seats or access features not included in the trial, you will need to upgrade to a paid subscription. You can chat with LivePerson sales on liveperson.com or from the connection area within LiveEngage to get help from a specialist to find the right package for your business.

If you already have a LiveEngage account, you can use that account instead of a creating a free trial account. However, we recommend creating a new account to make sure that any changes and customizations you make do not affect your site visitors until you are ready to launch them.

Some features to get started with include:

  • Messaging and push notifications
  • Bot for User type
  • Authenticated chat
  • Audio messaging
  • Vibrate on new incoming message
  • Photo sharing

Step 2. Retrieve your domain

Before you get started with any LivePerson API, you must retrieve the base domain of LivePerson using the Domain API (a read-only API). More information on using the Domain API can be found here.

Step 3. Select the login method

In this step, you choose whether to access LiveEngage sessions with the User Login or Application Login method.

User Login

The User Login method provides a way for users to access and manage a LiveEngage session. A session could be a customized workspace or hosting a LiveEngage user in an external app. Use the LiveEngage username and password.

Logged in users are managed under the same restrictions as regular users in LiveEngage, including password expiration, concurrent conversation limits, skill groups and so on. If your account has SSO enabled, this method is not standalone, and you must register the relevant user through your hub to provide LiveEngage with an SSO SAML assertion.

Application Login

The Application Login method provides a way for applications to access and manage LiveEngage sessions, such as bots, virtual agents, or other apps that need to act as an agent. The Application Login method overcomes both issues detailed in the User Login method (above), such as password expiration or SSO integration.

To log in as an application, you must have the User Type - Bot feature activated. If you do not, contact your account team before proceeding.



Step 4. Authorize API Calls

In this step, now that you’ve chosen your login method. Some of our APIs require authorization before you can use them. Every API uses either user login credentials or an API key, or both, which you can find in the overview of the API itself.

  1. Use the Login Service API to log into LiveEngage to get a session token (Bearer) to use for other related API calls. You can log in as a user with credentials or an application with an API key.

  2. Use this token in your authentication header in the following API calls:

    • Users API - updates the LiveEngage user list on regular intervals

    • Login Service API - provides endpoints to manage the user session in LiveEngage

    • Domain API - retrieves the base domain of LivePerson



Step 5. Create an API key

Application keys are security tokens that you use to log into LiveEngage. The application key gets installed automatically and assumes the security settings granted to the associated user in LiveEngage.

More information on using the API key can be found here.



Next steps

Congratulations! You are now ready to customize and implement features in LiveEngage.

  • Integrate LiveEngage with iOS and Android apps to create and manage digital engagements. Additionally, customers can communicate with the brand's agents through their channel of choice. For more information, refer to the Mobile Messaging SDK for Android or iOS.

  • Enable consumer monitoring and engagement flows to gather reporting data about the consumer, engagements, and campaigns. By combining monitoring capabilities with our Campaigns feature, you can display tailored engagements to the right consumer at the right time. For more information, refer to the Monitoring API.

  • Integrate a messaging bot into LiveEngage to send/receive text messages, send structured content, transfer the conversation to other skills, change Time To Response, and close a conversation. You use the Agent Messaging SDK to connect a bot, but your account must be enabled to support bot users. To check the enabled features for your account, contact your account team or LivePerson Support.

  • Manage users in LiveEngage to update user lists that may need updating on a regular basis. You use the Users API to make updates such as profile pictures, login names, passwords, or user assignments. You can also synchronize any HR or staffing system with LiveEngage.

  • Implement a retry policy. We recommend that you add a mechanism to your API call to increase reliability and stability. Each component in a network can return an error, which can cause your application to fail. If an error returns, the mechanism makes sure that your application attempts to retrieve the relevant information. More information on our retry policy best practices can be found here.