Realtime API

The Realtime API provides programmatic access to ongoing activity in your Tiledesk server.
The Realtime API is implemented using WebSocket technology.
You can use the API to do the following:
Display requests data
Display agents data
Create and display a real-time dashboard
Predict or estimate capacity and other derived metrics
The Realtime API allows you to receive events from Tiledesk after you subscribe to one or more topics.
This API is an SSL-only API. You must be a verified user to make API requests. You can authorize against the API using JWT token.
Topics
Topic
Description
/PROJECT_ID/requests
Get the last open requests of a project
/PROJECT_ID/requests/REQUEST_ID
Get the requests detail
/PROJECT_ID/requests/REQUEST_ID/messages
Get the request messages
/PROJECT_ID/project_users/PROJECT_USER_ID
Get the agents info
Rate Limiting
We only allow a certain number of new connections per minute. The number of new connections to the Realtime API is restricted by REST API rate limits. We also allow a certain number of concurrently running connections to the Realtime API.
We reserve the right to adjust the rate limit for given endpoints in order to provide a high quality of service for all clients. If the rate limit is exceeded, Tiledesk will respond with a body that details the reason for the rate limiter kicking in.
We also limit the total amount of data exchanged through real time APIs. For example the number of Realtime requests exchanged can’t exceed a certain number of items. If this number is exeeded you can always use REST APIs to get additional data or to make more complex queries.
Using The API
Establish an authenticated WebSocket connection to wss://eu.rtm.tiledesk.com/v2/ws/.
Subscribe to one or several topics.
Process incoming events.
Unsubscribe to topics.
Allowed For
Owner
Administrator
Agent
Establish Connection
Connect to the wss://eu.rtm.tiledesk.com/v2/ws/ WebSocket endpoint using your JWT token.
1
  var ws = new WebSocket("wss://eu.rtm.tiledesk.com/v2/ws/?token=YOUR_JWT_TOKEN"); 
2
​
3
  ws.onopen = function () {
4
      console.log('websocket is connected.');         
5
  }
6
​
7
  ws.onclose = function () {
8
      console.log('websocket is closed.');           
9
  }
10
​
11
  ws.onerror = function () {
12
      console.log('websocket error ...')
13
  }
Copied!
Subscribe to a topic
Once connection is established, you can send messages to subscribe to individual topics. Refer to Topics for the topic key.
1
{
2
   "action":"subscribe",
3
   "payload":{
4
      "topic":"/<YOUR_PROJECT_ID_HERE>/requests"
5
   }
6
}
Copied!
To subscribe to a topic you can execute :
1
ws.send(JSON.stringify(subscriptionMessage));
Copied!
Example:
1
var subscriptionMessage =
2
{
3
   "action":"subscribe",
4
   "payload":{
5
      "topic":"/5df26badde7e1c001743b63c/requests"
6
   }
7
}
8
​
9
ws.send(JSON.stringify(subscriptionMessage));
Copied!
Process Incoming Events
Once you have subscribed to one or several topics, listen to subsequent messages to start collecting data.
1
 ws.onmessage = function(message) {   
2
    console.log(message);
3
    try {
4
         var data = JSON.parse(message.data);
5
    } catch (e) {
6
       return console.log('This doesn\'t look like a valid JSON: ', message.data);
7
    }
8
​
9
   //.... ADD YOUR LOGIC HERE    
10
}
Copied!
The following are sample messages received after subscribing to requests topic:
1
{
2
   "action":"publish",
3
   "payload":{
4
      "topic":"/5eb45fbc1f9e1f0012d62207/requests",
5
      "method":"CREATE",
6
      "message":[
7
         {
8
            "_id":"5eb4fc911f9e1f0012d62248",
9
            "status":200,
10
            "preflight":false,
11
            "participants":[
12
               "5eb45fb21f9e1f0012d62201"
13
            ],
14
            "request_id":"support-group-1a952f2f-c09a-46be-bc75-11387a95d55f",
15
            "requester":"5eb45fbc1f9e1f0012d62208",
16
            "lead":{
17
               ...
18
            },
19
            "first_text":"hello world",
20
            "department":"5eb45fbc1f9e1f0012d62209",
21
            ...
22
            "assigned_at":"2020-05-08T06:30:41.090Z",
23
            "id_project":"5eb45fbc1f9e1f0012d62207",
24
            "createdBy":"5eb45fb21f9e1f0012d62201",
25
            "tags":[
26
​
27
            ],
28
            "notes":[
29
​
30
            ],
31
            "channel":{
32
               "name":"chat21"
33
            },
34
            "createdAt":"2020-05-08T06:30:41.094Z",
35
            "updatedAt":"2020-05-08T06:31:00.367Z",
36
            "__v":0,
37
            "first_response_at":"2020-05-08T06:30:58.109Z",
38
            "waiting_time":17015,
39
            "id":"5eb4fc911f9e1f0012d62248",
40
            ....
41
         },
42
         ..
43
      ]
44
   }
45
}
Copied!
Unsubscribe
Once you stop processing some data, you can individually unsubscribe from a topic. Events will then stop being pushed on the connection.
1
{
2
   "action":"unsubscribe",
3
   "payload":{
4
      "topic":"/<YOUR_PROJECT_ID_HERE>/requests"
5
   }
6
}
Copied!
Example
You can find a simple example of the Tiledesk Realtime API here​

Subscriptions

Next - APIs

JWT Authentication

Last modified 1yr ago

Copy link

Contents

Process Incoming Events

Unsubscribe

Example