I have gotten a lot of request from people on how to connect to the APIs that are available from LivePerson using Postman, so I decided to share how to do this here. In order to follow along with this tutorial, you will need the API keys that are available for Engagement History API, and you will need access to the Postman App. To get these keys, you can log into the LiveEngage console, and grab them from them from the API tab under data sources, which is on the campaigns tab.

Last weekend a few friends from work and I decided to enter Ludum Dare. Ludum Dare is one of the longest running game jams that happens every April, August, and December. It has been around for 12 years, and we finally decided to enter this time around. It was a really interesting experience, since you have a strict deadline to make a game, and you do not receive the theme of the game jam until the jam starts.

The Engagement History API is an API that is available from LivePerson, and it allows for you to search, filter, and keep copies of chat transcripts and the related data, such as visitor information, agent information, and much more. Before writing any code to start querying the API, it can be useful to use a tool that will allow for you to connect to the API in seconds. This article discusses how you can use the RESTClient query to the Engagement History API.

When it comes time to connect to APIs, I find that it is a lot easier to test them using a REST client before you start writing any code. Using a REST client allows for you to make sure that you are able to connect to it successfully, and it allows for you to try out different parameters of the API. One of the best tools that I was introduced to is, the Firefox RESTClient Plugin.

Hi Everyone, I know it has been awhile since my last post here, so I just wanted to give everyone a quick update. I haven’t had a lot of time to create content rich posts since I have had a few life changes in the past 2 months. I ended up fracturing my ankle mid February, so my daily routine has changed quite a bit, and I had been asked to create blog posts for the new support community at LivePerson, so I have been focusing on creating content there.

Today I wanted to share with you a program I made that will allow you to use the Engagement History API to send out emails for transcripts that have a particular keyword. The program will use the API to pull all of your chat transcripts for the previous day that contain a certain keyword, and then it will send it to an email address that you specify. The program makes use of the SendGrid API in order to send the emails.

Update: With the new HTML engagements in LiveEngage, this method is now outdated. It is recommended that you use the supported method listed above. The purpose of this tutorial is to show you how you can use your own chat buttons with LiveEngage by using JavaScript. Currently in LiveEngage, you have a limited number of options for creating a chat button in the LiveEngage studio. This can make it hard for the chat button to match the look of your site, especially with all of the things you can do with CSS and JavaScript today.

Today I wanted to share with everyone a website that I came across and that I have started using: http://www.freecodecamp.com/ Free Code Camp is a community that provides to you hundreds of hours of coding lessons, a way to build your portfolio, and they will put you in touch with non-profit organizations that will allow you to apply your new skills. Some of the skills you can learn include: HTML5 CSS3 JavaScript Databases Git and GitHub Node.

Adobe will be holding another “AEM Gem” on January 20th at 11 A.M. - 12:00 P.M. EST. This session will be a technical deep dive on Oak Lucene Indexes and how they can be used to get your queries perform better. This gem will also provide insight into how asynchronous indexing works and how it can be monitored. Here is a link to sign up if you are interested: Register

We are fast approaching the end of this year, and I just wanted to thank everyone that has stopped by and read some of my posts. This was my 1st year of maintaining a blog, and what a learning experience it has been. Initially, I started this blog as a way to share what I had learned on AEM, and I was able to share a lot of information. However, with a career change, and not knowing how popular some of the posts where going to be, I had to start allocating time for comments, and time to improve general design of my blog.