Skip to main content

Rest API


This article explains how to use the REST API response type in a bot. With this feature, you can integrate any third-party API without any coding.

In order to make it work, you need to set up two things:

Rest API Call

The REST API call building window is built in such a way that you can execute almost any request you want.

Fields Definition for REST API


Name for your own purposes.


Description for your own purposes.


This should be a non-changing URL part. To this part, the Sub URL part is always appended.

Add request

This button adds new request options to this API. You can have as many requests as you want. The request name is visible in the trigger method choosing dropdown.

Request fields

Name of the request

Visible in the method choosing dropdown in the trigger.


The appropriate method type for the request.


URL to append to the host. It can be one of the replaceable variables.


In the Params section, you define arguments that should be accessible as GET parameters.


If you are using an authorized API, you can set up basic authorization methods there.


These values will be added to the header. They are combined like this:

<Key>: <value>


The body can be sent either as RAW, also known as JSON Body, or as regular POST parameters.

User parameters

These parameters can be entered directly in the bot trigger itself once the method is chosen.

If you choose Body Param, you can use this variable Location/Key as a replaceable variable in your body JSON content.


If you choose Query or Body Post Param, the key will be used as a post/get parameter directly.

In Rest API

In the trigger, it would look like

Output parsing

Output parsing is dedicated to extracting useful variables from the API response.


The name will be visible within the option to execute a specific trigger based on the response.

In the trigger, it will be visible here

HTTP status code E.g 200,301,500

For this response to match, you can define the expected HTTP status code. It's optional. This way you can separate the success response from the failed one.

Response Location 1/2/3/4/5/6.

If you define a success location, it will parse the response as JSON and try to extract the specified attribute.

Examples of variable extraction:

status as location value would return success

"status": "success"

response:location as a location value would return Lithuania

"response": {
"location" : "Lithuania"

items:0:name as a location value would return Sub item name

"items": [
"name" : "Sub item name"

links:link:[type=forms]:url as a location value would return an element where the type is forms

"links": {
"link": [
"type": "prices",
"url": {},
"chat_message": "We do not have that information available online. We could follow up with you directly to discuss."
"type": "forms",
"url": "",
"chat_message": "You can view and download our forms on this page"
Parsing array for the output
  • user_info:phones^implode=={n} would output phones array combined with new line character.
  • user_info:phones^implode==[b]{item}[/b]{n} would output phones array wrapper with bold and new line character
"user_info": {
"phones": [
Parsing XML for the output

when you parse xml you should omit first tag and start from the second tag:

  • use pin:value, NOT response:pin:value

Conditions checking

Sometimes it makes sense to check was something found based on response attribute. So you can define condition to check.

Here we expect that status value would be success.

JSON should look like this

"status": "success"

Meta msg location.

Here we can extract meta_msg if you provide Live Helper Chat compatible JSON response. Meta message will be used in chosen response trigger [text message] if this trigger does not have any meta message information.

"msg": "Standard message text from REST API",
"meta_msg": {
"content": {
"quick_replies": [
"type": "button",
"content": {
"name": "Rest API Button",
"payload": "rest_api_button"

In order for rest API to receive these clicks you should also check in trigger Default for unknown button click


Each trigger at the bottom has Show code button. This code is supported only by Execute trigger body response type. If you just want to build trigger and get code for response and reuse it, it's the response type you should use instead.


Only if these conditions are met we will send Rest API request. Usefull in webhook cases.

Let say you want to send request only if chat happened with a bot?

Condition for that chat could look like

In case you want to send Rest API only if user message is not empty sample would look like

{{msg_clean_lowercase}} != // Do not enter anything

Replaceable variables

Rest API in value fields you can use these replaceable variables. These variables by default are already in json format with quotes. To use them without quotes in JSON payload use them like raw_{{lhc.nick}}, etc. raw_{{}}

All chat messages. These combinations are usefully in case you are implementing sentiment analysis and want for example determine the sentiment of operator/visitor or both messages:

You can quickly explore all possible chat attributes by clicking Explore possible chat attributes directly. link in Rest API builder interface next to Add request button. This option is also available in Audit Logs section.

Single messages

  • {{msg}} - user/operator message.
  • {{msg_lowercase}} - user/operator message. Lowercase version.
  • {{msg_url}} - user/operator message will contain links instead of bbcode tags.
  • {{msg_url_lowercase}} - user/operator message will contain links instead of bbcode tags. Lowercase version.
  • {{msg_clean}} - user/operator message without [file=616_6f13fafc726e119f5a0a3f49221b45f7] in it's body if it's the only content in message.
  • {{msg_clean_lowercase}} - user/operator message without [file=616_6f13fafc726e119f5a0a3f49221b45f7] in it's body if it's the only content in message. Lowercase version.
  • {{msg_html}} - msg in HTML format
  • {{msg_html_lowercase}} - msg in HTML format lowercase
  • {{msg_html_nobr}} - msg in HTML format without <br /> tags. Presently used in telegram integration.
  • {{msg_html_lowercase_nobr}} - msg in HTML format lowercase without <br /> tags.

All messages at once

  • {{msg_all_since_transfer_content}} - Messages since chat was transferred to operator. All messages without [<date>] [<nick>] prefix within each message. System messages are not printed.
  • {{msg_all_op_msg_content}} - All operator messages in the chat. All messages without [<date>] [<nick>] prefix within each message.
  • {{msg_all_vis_msg_content}} - All visitor messages in the chat. All messages without [<date>] [<nick>] prefix within each message.
  • {{msg_all_vis_since_transfer_content}} - All visitor messages in the chat since operator took over the chat. All messages without [<date>] [<nick>] prefix within each message.
  • {{msg_all}} - all chat messages.
  • {{msg_all_conversation}} - all chat messages without system and whisper messages.
  • {{msg_items}} - all chat messages objects encoded in JSON. Just do json_decode on passed variable
  • {{msg_all_html}} - all chat messages rendered as HTML. You might need to style classes.
  • {{msg_all_content}} - all messages without [<date>] [<nick>] prefix within each message. System messages are not printed.
  • {{media_all}} - array of files attached [file... syntax.
  • {{media_all_links}} - plain text with structure of
    • [file_1.pdf] [file_2.pdf]
* `{{media_all_links_raw}}` - plain text with structure of 
* ```
  • {if_previous_visitor_messages}{"content":{{previous_visitor_messages_url__100}},"role":"user"},{/if_previous_visitor_messages} print last 100 messages if there is any. We print here only visitor last 100 messages.


  • {{ip}} - visitor ip. If you are running background worker this value will be localhost.
  • {{footprint}} - last 25 viewed pages url's
  • {{chat_id}} - chat ID
  • {{timestamp}} - unix timestamp
  • {{subject_ids}} - array of subject id's assigned to chat
  • {{subject_list}} - array of subjects objects with all attributes
  • {{subject_list_names}} - string of subject names imploded by comma
  • {{survey}} - filled chat surveys

Attributes usefull for sending content in Sub URL for file

  • {{file_body}} - base64 encoded file content 'data:'.$mediaFile->type.';base64,'.base64_encode(file_get_contents($mediaFile->file_path_server));
  • {{file_url}} - url to download file directly
  • {{file_name}} - uploaded file name from operator

Additional attribute you can use for Sub URL for file and If you are sending file you can have a different body content

  • {file_api}your request body in case it's a file{/file_api}
  • {image_api}your request body in case it's an image{/image_api} - 'image/jpeg','image/png','image/gif'
  • {vodeo_api}your request body in case it's an image{/vodeo_api} - 'video/mp4'

You can have dynamic variable based on file extension by using {api_by_ext__<file_type>_<other_file_type>}sendVoice{/api_by_ext} E.g

  • {api_by_ext__ogg}sendVoice{/api_by_ext} - use sendVoice value if media file extension is ogg
  • {api_by_ext__mp3_m4a}sendAudio{/api_by_ext} use sendAudio value if media file extension is mp3 or m4a

Same pattern has to be defined in Sub URL for file and If you are sending file you can have a different body content fields.

Example from telegram. Sub URL for file file url


Example from telegram. If you are sending file you can have a different body content file content


Additional attributes you can use

  • {interactive_api}quick reply buttons wrapper{/interactive_api}
  • {button_template}quick reply individual button template{/button_template}
  • {is_button}"button"{/is_button} - in case quick reply button is a button
  • {is_url}"url"{/is_url} - in case quick reply button is an url
  • {{rest_api_button}} - custom content from bot builder Rest API button custom content. field
  • {{button_payload}} - either lhc genrared internal payload for the trigger execution or just an URL
  • {{button_title}} - quick reply button title
"name":"Live Helper Chat"
,"keyboard": {
"Type": "keyboard",
"Buttons": [
"ActionBody": {{button_payload}},

Main chat attributes. You can access only first level attributes.

  • {{lhc.nick}} - visitor nick
  • {{}} - e-mail
  • {{lhc.department}} - department name
  • {{lhc.dep_id}} - department ID
  • {{lhc.<any chat attribute>}} - all possible attributes you can find at the bottom under Models > Chat also you can access any dynamic attribute like {{lhc.department_name}}.

To access custom passed variables or fields.

  • {{lhc.add.<additional variable key/identifier>}} - these values you are passing additionaly. It's either Field identifier from Start a chat form settings > Custom fields or if you are passing manually it's name attribute. If you put Field identifier value as gender in Start a chat form settings > Custom fields. In Rest API Call you can access this field like {{lhc.add.gender}}
  • {{lhc.var.<chat variable key>}} - these values can be set using extensions etc. It's data is taken by json_decode function from chat_variables column value. This column stores JSON as {<key> : <value>,..}. Usually in this column extensions stores their own data.
  • {{media}} - Will hold JSON encoded related files to send message.
"id": 636,
"size": 10007,
"upload_name": "image.png",
"type": "image/png",
"extension": "png",
"hash": "4bcda854ef4f27e8b4003b42c84f1cb6",
"url": ""

Dynamic attributes extraction. You can go as deep as you want.

  • {{args.<any argument attribute>.<any subargument attribute>}} - if you are implementing webhooks most likely you will be using this as placeholder.
  • {{}} - This way you can access any chat and child object attributes. In this example department identifier.
  • {{}} - you can pass even all department object.
  • {{}} - access order_id if field is defined as This variable is invisible for operator and will be stored in chat_variables attribute
  • {{}} Chat object also see __get method for magic attributes like
    • department or user
      • {{}} name visible in the widget or
      • {{}} name visible in the back office
  • {{args.arg_1}} - commands arguments

Incoming chat attributes. This is usefull if you want to access to payload attribute of Incoming webhook created chat.

  • {{}} - external chat id
  • {{}} - first part of chat external if two fields are used
  • {{}} - last part of chat external if two fields are used
  • {{*}} - you can access any first payload attribute. E.g session Id
  • {{<you defined key in attribtues of incoming webhook>}} - you can use this as placeholder for Sub URL or Sub URL for file. Just leave empty host attribute.
  • {{}} - you can access any attribute of incoming webhook definition
  • {{args.msg_text}} - unknown button click payload value

All possible models attributes you can find at the bottom under Models > Chat

These are the main classes

All classes can be found here


So your JSON body in rest API can look like

"msg":{{msg}}, // OR {{msg_clean}}
"subject_ids": {{subject_ids}}

Replaceable variables works only in

  • Params
  • Body
  • Headers

Trigger workflow

In trigger once everything is setup it will look like this.

Fields description

  • Rest API - it's our main Rest API Name we are working with
  • Method - it's our Name of the request from Rest API building window.
  • User entered parameter - it's just defined parameter which is coming from Rest API builder window User parameters tab.
  • Execute trigger for [UUID Set] - It's defined output parsing option which we defined in Rest API Output parsing tab.
  • Default trigger to execute - if we did not found any matching output combination this trigger will be executed.
  • Send Rest API Call in the background. - by default Rest API calls are send as soon visitor sends a message, they are happening on same request. This can lead to a problems if Rest API is slow. We can send Rest API calls in the background, but for that you have to be running lhc-php-resque extension. You won't need to code anything just setup extension itself.
  • Process on next visitor message - this call will be executed only on next visitor message. Usefull in case you want to check only for specific actions.
  • Save response as system message - will save a message as system message. It will be invisible for the visitor.
  • Do not save response. - usefull in case you want to execute a call, but do not save any related information.

Example of Process on next visitor message

Output variables in triggers

Use can use these variables in your text triggers response text.

  • {content_1}
  • {content_2}
  • {content_3}
  • {content_4}
  • {content_5}
  • {content_6}
  • {http_code} - https status code returned from request
  • {http_error} - additional error explanation from curl_error($ch);
  • {content_raw} - raw response returned from Rest API call without any parsing
  • {http_data} - Request parameters used for rest api call.

How to iterate through response if content_[n] holds an array?

Text message content can look like this. Your iterable object will be available under {args.item.<internal property of you object> attribute.

- {args.item.mail_asesor}

There variables can be used in most of the response types including

How to pass in what language chat is going?

Best way is just to pass {{}} if customer is chatting in any other language than english, and you pass lang argument it's value will be always content_language attribute from siteaccess settings.

How to find out problems with Rest API

  • Setup output combination for success call.
  • In default response have two text messages as response

In rest api define trigger for Unknown unmatched output combination

In response have something like this. Pay attention second text message is send as system message.

How to handle API Errors?

The easiest way is set fallback trigger on Default trigger to execute. If API works correctly your defined output combination will be executed.

Events you can listen

See this extension sample

You can also see directly in the code for the events it dispatches

Video usage example