Web API Reference
Introduction
Versioning
This document describes the Customer Chat Web API v3.2. This is the deprecated version. We encourage you to migrate to the latest stable version. Read more about versioning...
Lifecycle headers
API responses will contain one of two headers related to the API lifecycle: Legacy
or Deprecation
. These headers specify when the associated stage ends (in the YYYY-MM-DD
format).
What is Web API
Web API is similar to REST API. Client can send a request message that results in getting a response message. It's also possible to get webhooks.
When to use Web API
If you're wondering which API to use - Customer Chat RTM API or Web API, keep on reading.
Web API allows for building stateless integrations. The communication is done via XHR requests. The implementation is easier than with RTM API, but you need to take possible time delays into consideration.
Not what you're looking for? Perhaps, you need to use Customer Chat RTM API instead.
Access
Customer authentication is handled with access tokens. Find out how to get an access token from Customer authorization flow. Take note that it's not the same token you would use for the Agent Chat or Configuration API.
Data centers
LiveChat system operates in two data centers: dal
(USA) and fra
(Europe). The default data center is dal
.
All the LiveChat OAuth 2.1 access tokens have a prefix: dal:
or fra:
. This prefix indicates the data center they belong to. If you need to specify the data center while making an API call, simply add the X-Region: <token_prefix>
optional header.
Summing up, if the user token starts with fra
, you should add the X-Region: fra
header. If the token starts with, dal:
you don’t have to specify the header.
If you get the misdirected_request
error, use the prefix returned in the error as the value of X-Region
.
Postman Collection
You can find all the requests from the Customer Chat Web API v3.2 in Postman. In our collection, we use environment variables for the API version and the access token. Importing the collection from the link below downloads the LiveChat Web API environment as well. Remember to replace the sample token with your own.
Data structures
To find sample payloads of events, users, and other common structures such as chats or threads visit the Data structures document.
Methods
HTTP method | The API endpoint | Methods |
---|
POST | https://api.livechatinc.com/v3.2/customer/action/<action> | All except for Get License Properties and Get Group Properties |
GET | https://api.livechatinc.com/v3.2/customer/action/<action> | Get License Properties and Get Group Properties |
Header | Value | Notes |
---|
X-API-Version | 3.2 | Not needed if you specify the API version in the URL. |
Content-Type | multipart/form-data; boundary=<boundary> | Valid for the Upload File method |
Content-Type | application/json | Valid for every method except for Upload File |
Authorization | Bearer <token> | Customer access token. It's not the same token you would use for the Agent Chat or Configuration API. Not needed for Get License Properties and Get Group Properties. Read more... |
Response Header | Value | Notes |
---|
Legacy | YYYY-MM-DD | The date when the legacy stage ends. |
Deprecation | YYYY-MM-DD | The date when the deprecated stage ends. |
Every request to Customer Chat API needs to have the following query string parameters:
Query string parameter | Data type | Notes | Methods |
---|
license_id | integer | LiveChat account ID | All |
Available methods
Chats
List Chats
It returns summaries of the chats a Customer participated in.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/list_chats |
RTM API equivalent | list_chats |
Webhook | - |
Request
Parameter | Required | Type | Notes |
---|
limit | No | number | Default: 10, maximum: 25 |
sort_order | No | string | Possible values: asc , desc (default). Chat summaries are sorted by the creation date of its last thread. |
page_id | No | string | |
Response
Field | Data type | Notes |
---|
total_chats | number | An estimated number. The real number of found chats can slightly differ. |
next_page_id | string | In relation to page_id specified in the request. Appears in the response only when there's the next page. |
previous_page_id | string | In relation to page_id specified in the request. Appears in the response only when there's the previous page. |
chats_summary | array | Array of Chat summary data structures. |
List Threads
It returns threads that the current Customer has access to in a given chat.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/list_threads |
RTM API equivalent | list_threads |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | |
sort_order | No | string | Possible values: asc - oldest threads first and desc - newest threads first (default). |
limit | No | number | Default: 3, maximum: 100 |
page_id | No | string | |
min_events_count | No | number | Range: 1-100; Specifies the minimum number of events to be returned in the response. It's the total number of events, so they can come from more than one thread. You'll get as many latest threads as needed to meet the min_events_count condition. |
You cannot use both limit
and min_events_count
at the same time.
Get Chat
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/get_chat |
RTM API equivalent | get_chat |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | |
thread_id | No | string | Default: the latest thread (if exists) |
Start Chat
Starts a chat.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/start_chat |
RTM API equivalent | start_chat |
Webhook | incoming_chat |
Request
Parameters | Required | Data type | Notes |
---|
chat | No | object | |
chat.properties | No | object | Initial chat properties |
chat.access | No | object | Chat access to set; default: all agents. |
chat.thread | No | object | |
chat.thread.events | No | array | Initial chat events array. Does not support the form type event in the LiveChat app. |
chat.thread.properties | No | object | Initial thread properties |
continuous | No | bool | Starts chat as continuous (online group is not required); default: false . |
Response
Field | Data type | Notes |
---|
chat_id | string | |
thread_id | string | |
event_ids | []string | Returned only when the chat was started with initial events. Returns only the IDs of user-generated events; server-side generated events are not included in the array. |
Activate Chat
Used to restart an archived chat.
Specifics
Request
Parameter | Required | Type | Notes |
---|
chat | Yes | object | |
chat.id | Yes | string | ID of the chat that will be activated. |
chat.access | No | object | Chat access to set; default: all agents. |
chat.properties | No | object | Initial chat properties |
chat.thread | No | object | |
chat.thread.events | No | array | Initial chat events array |
chat.thread.properties | No | object | Initial thread properties |
continuous | No | bool | Sets a chat to the continuous mode. When unset, leaves the mode unchanged. |
Response
Field | Data type | Notes |
---|
thread_id | string | |
event_ids | []string | Returned only when the chat was activated with initial events. Returns only the IDs of user-generated events; server-side generated events are not included in the array. |
Deactivate Chat
Deactivates a chat by closing the currently open thread. Sending messages to this thread will no longer be possible.
Specifics
Request
Parameter | Required | Data type | |
---|
chat_id | Yes | string | |
Response
No response payload (200 OK
).
Events
Send Event
Sends an Event object. Use this method to send a message by specifying the Message event type in the request.
The method updates the requester's events_seen_up_to
as if they've seen all chat events.
Specifics
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | Id of the chat that you to send a message to. |
event | Yes | object | Event object. Does not support the form type event in the LiveChat app. |
attach_to_last_thread | No | bool | The flag is ignored for active chats. For inactive chats: true – the event will be added to the last thread; false – the request will fail. Default: false . |
Upload File
Uploads a file to the server as a temporary file. It returns a URL that expires after 24 hours unless the URL is used in send_event
.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/upload_file |
RTM API equivalent | - |
Webhook | incoming_event * |
*)
incoming_event
returns a URL that never expires.
Request
Parameter | Required | Data type | Notes |
---|
file | Yes | binary | Maximum size: 10MB |
Send Rich Message Postback
Specifics
*) incoming_rich_message_postback
will be sent only for active threads.
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | |
event_id | Yes | string | |
postback | Yes | object | |
postback.id | Yes | string | Postback name of the button |
postback.toggled | Yes | bool | Postback toggled; true or false |
thread_id | Yes | string | |
Response
No response payload (200 OK
).
Send Sneak Peek
Sends a sneak peek to a chat.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/send_sneak_peek |
RTM API equivalent | send_sneak_peek |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | Id of the chat to send a sneak peek to. |
sneak_peek_text | Yes | string | Sneak peek text |
Response
No response payload (200 OK
).
Properties
Update Chat Properties
Specifics
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | Id of the chat you to set a property for. |
properties | Yes | object | Chat properties to set. You should stick to the general properties format and include namespace, property name and value. |
Response
No response payload (200 OK
).
Delete Chat Properties
Specifics
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | Id of the chat you want to delete properties of. |
properties | Yes | object | Chat properties to delete. |
Response
No response payload (200 OK
).
Update Thread Properties
Specifics
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | Id of the chat you want to set properties for. |
thread_id | Yes | string | Id of the thread you want to set properties for. |
properties | Yes | object | Chat properties to set. |
Response
No response payload (200 OK
).
Delete Thread Properties
Specifics
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | Id of the chat you want to delete the properties of. |
thread_id | Yes | string | Id of the thread you want to delete the properties of. |
properties | Yes | object | Thread properties to delete. |
Response
No response payload (200 OK
).
Update Event Properties
Specifics
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | Id of the chat you want to set properties for. |
thread_id | Yes | string | Id of the thread you want to set properties for. |
event_id | Yes | string | Id of the event you want to set properties for. |
properties | Yes | object | Chat properties to set. You should stick to the general properties format and include namespace, property name and value. |
Response
No response payload (200 OK
).
Delete Event Properties
Specifics
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | Id of the chat you want to delete the properties of. |
thread_id | Yes | string | Id of the thread you want to delete the properties of. |
event_id | Yes | string | Id of the event you want to delete the properties of. |
properties | Yes | object | Event properties to delete. You should stick to the general properties format and include namespace, property name and value. |
Response
No response payload (200 OK
).
List License Properties
Returns the properties of a given license. It only returns the properties a Customer has access to.
Specifics
| |
---|
HTTP Method | GET |
Method URL | https://api.livechatinc.com/v3.2/customer/action/list_license_properties |
RTM API equivalent | - |
Webhook | - |
Request
Query string parameter | Required | Data type | Notes |
---|
license_id | Yes | number | Id of the license you want to return the properties of. |
namespace | No | string | Property namespace to retrieve |
name | No | string | Property name |
List Group Properties
Returns the properties of a given group. It only returns the properties a Customer has access to.
Specifics
| |
---|
HTTP Method | GET |
Method URL | https://api.livechatinc.com/v3.2/customer/action/list_group_properties |
RTM API equivalent | - |
Webhook | - |
Request
Query string parameter | Required | Data type | Notes |
---|
license_id | Yes | number | Id of the license you want to return the properties of. |
group_id | Yes | number | Id of the group you want to return the properties of. |
namespace | No | string | Property namespace to retrieve |
name | No | string | Property name |
Customers
Update Customer
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/update_customer |
RTM API equivalent | update_customer |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
name | No | string | |
email | No | string | |
avatar | No | string | The URL of the Customer's avatar |
session_fields | No | []object | An array of custom object-enclosed key:value pairs. Respects the order of items. |
At least one optional parameter needs to be included in the request.
When updating customer data while the customer has an active chat, the update will take effect after the chat has ended.
Response
No response payload (200 OK
).
Set Customer Session Fields
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/set_customer_session_fields |
RTM API equivalent | set_customer_session_fields |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
session_fields | Yes | []object | An array of custom object-enclosed key:value pairs. Respects the order of items. Max keys: 100 |
Users Agent and referrer are updated by default using the browser’s headers.
Response
No response payload (200 OK
).
Get Customer
Returns the info about the Customer requesting it.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/get_customer |
RTM API equivalent | get_customer |
Webhook | - |
Response
| |
---|
name | Customer's name. Returned only if set. |
email | Customer's email. Returned only if set. |
avatar | Customer's avatar. Returned only if set. |
session_fields | An array of custom object-enclosed key:value pairs. Returned only if set. Available for the session duration. |
Status
List Group Statuses
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/list_group_statuses |
RTM API equivalent | list_group_statuses |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
all | No | bool | If set to true , you will get statuses of all the groups. |
group_ids | No | array | A table of groups' IDs |
One of the optional parameters needs to be included in the request.
Response
No response payload (200 OK
).
Response
| | |
---|
Group Not Found | If you send group_id of a group that doesn't exists, the id won't be included in the resposne. | |
Other
Check Goals
Customer can use this method to trigger checking if goals were achieved. Then, Agents receive the information. You should call this method to provide goals parameters for the server when the customers limit is reached. Works only for offline Customers.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/check_goals |
RTM API equivalent | - |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
session_fields | Yes | []object | An array of custom object-enclosed key:value pairs |
group_id | Yes | number | |
page_url | Yes | string | |
Response
No response payload (200 OK
).
Get Form
Returns an empty ticket form of a prechat or postchat survey.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/get_form |
RTM API equivalent | get_form |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
group_id | Yes | number | Id of the group from which you want the form. |
type | Yes | string | Form type; possible values: prechat or postchat |
Response
Field | Notes |
---|
enabled | If enabled: false , the form object is not returned. Prechat/postchat survey disabled in the LiveChat Agent App UI. |
form | The form object |
Get Predicted Agent
Gets the predicted Agent - the one the Customer will chat with when the chat starts. To use this method, the Customer needs to be logged in, which can be done via the login
method.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/get_predicted_agent |
RTM API equivalent | get_predicted_agent |
Webhook | - |
Get URL Info
It returns the info on a given URL.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/get_url_info |
RTM API equivalent | get_url_info |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
url | Yes | string | Valid website URL |
Response
Field | Data type | Notes |
---|
image_url | string | URL of the minified image hosted on the LiveChat's CDN |
image_original_url | string | URL of the original image |
Mark Events As Seen
Specifics
Request
Parameter | Required | Data type | Notes |
---|
chat_id | Yes | string | |
seen_up_to | Yes | string | RFC 3339 date-time format |
Response
No response payload (200 OK
).
Accept Greeting
Marks an incoming greeting as seen.
How it's implemented in LiveChat:
The Chat Widget uses this method to inform that a Customer has seen a greeting. Based on that, the Reports section displays the greetings
that were actually seen by Customers, not all the sent greetings. If a Customer started a chat from a greeting, but the Accept Method wasn't executed,
the greeting is still counted as seen in Reports.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/accept_greeting |
RTM API equivalent | accept_greeting |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
greeting_id | Yes | number | ID of the greeting configured within the license to accept. |
unique_id | Yes | string | ID of the greeting to accept. You can get it from the incoming_greeting push. |
Response
No response payload (200 OK
).
Cancel Greeting
Cancels a greeting (an invitation to the chat). For example, Customers could cancel greetings by minimalizing the chat widget with a greeting.
Specifics
| |
---|
Method URL | https://api.livechatinc.com/v3.2/customer/action/cancel_greeting |
RTM API equivalent | cancel_greeting |
Webhook | - |
Request
Parameter | Required | Data type | Notes |
---|
unique_id | Yes | string | ID of the greeting to cancel. You can get it from the incoming_greeting push. |
Response
No response payload (200 OK
).
Webhooks
Here's what you need to know about webhooks:
- Webhooks notify you when specific events are triggered.
- They can be generated by both Web and RTM API actions.
- When using RTM API, you can be also notified about events with pushes.
- Webhooks and pushes have similar payloads.
See webhook methodsSee webhook payloadsErrors
Possible errors
Error type | Default message | Description |
---|
authentication | Authentication error | An invalid or expired access token. |
authorization | Authorization error | User is not allowed to perform the action. |
customer_banned | Customer is banned | The customer had been banned. |
entity_too_large | Upload limit exceeded (10MB). | Client's request is too large. |
greeting_not_found | Greeting not found | |
group_not_found | Group not found | |
group_offline | Group is offline | Thrown in response to Get Predicted Agent. |
group_unavailable | No agent available for group | Thrown in response to Get Predicted Agent. The group is online, but there are no available Agents. |
groups_offline | Groups offline | |
internal | Internal server error | |
license_expired | License expired | The end of license trial or subcription. |
license_not_found | License not found | License with the specified ID doesn't exist. |
misdirected_request | Wrong region | Client's request should be performed to another region. The correct region is returned in the optional data object – this is where the client should be connected. |
request_timeout | Request timed out | Timeout threshold is 15 seconds. |
too_many_requests | Too many requests | The request's rate limit was exceeded. It'll be unblocked automatically after some time. |
unsupported_version | Cannot call unsupported API versions. | Unsupported protocol version. |
validation | Wrong format of request | |
wrong_product_version | Wrong product version | License is not LiveChat 3 (probably still LiveChat 2). |
Contact us
If you found a bug or a typo, you can let us know directly on GitHub.
In case of any questions or feedback, don't hesitate to contact us at developers@text.com. We'll be happy to hear from you!