Session service provides showing pub/sub status to ThingScale's built-in message broker.
Both MQTT and WebSocket clients shown in session.

On this page:

Showing active pub/sub sessions

Endpoint

URI	HTTP Method
https://m.thingscale.io/v2/session	GET

Parameter

Request Parameters

Request Parameter	Description
Header:	X-APITOKEN:`API_TOKEN_HERE`
Body:	None

Response Body

Response body is return in JSON

Elements	Type	Description	API version
client_id	string	MQTT client_id	2.x
ipaddress	string	Client's IP address	2.x
clean_sess	boolean	MQTT clean session capability	2.x
proto_ver	int	MQTT protocol version	2.x
keepalive	int	MQTT keepalive timer	2.x
connected_at	string	pub/sub connection initiate time(ISO_8601)	2.x

Sample Payload

[
    {
        "client_id": "mosqsub/14968-stg.testclient",
        "ipaddress": "XXX.XXX.XXX.XXX",
        "clean_sess": true,
        "proto_ver": 3,
        "keepalive": 60,
        "connected_at": "2017-10-22T16:28:39+0900"
    },
    {
        "client_id": "mqttjs_4a27d72261",
        "ipaddress": "XXX.XXX.XXX.XXX",
        "clean_sess": true,
        "proto_ver": 4,
        "keepalive": 60,
        "connected_at": "2017-10-22T16:39:00+0900"
    }
]

Response Code

HTTP Status Code: Description/Response Body:

200 OK Transaction OK.

401 Unauthorized

APITOKEN is invalid or null

{"error" : "AUTH_REQUIRED"}

404 Not Found

no active session found

{"error" : "NO_SESSION"}

About how to see the session

If Publish from the device to the message broker is not a persistent session and disconnects the payload every time it is sent out, the session will be terminated in a very short period of time, so it is not possible to catch the session in most cases.
When a device subscribes to a message broker, it is inevitably a persistent session so it can be caught until the session ends.