List subscriptions message format

List subscriptions requests must be sent as JSON in text frames, one request per frame. This message is different from others as it doesn't require you to provide subscription ID. Thus, the response for this message is different too.

Example of request

_10

{

_10

"action": "list_subscriptions"

_10

}

Example of response

_17

{

_17

"subscriptions": [

_17

{

_17

"subscription_id": "some-id-1",

_17

"topic": "blocks",

_17

"arguments": {

_17

"block_status": "finalized",

_17

"start_block_height": "123456789"

_17

}

_17

},

_17

{

_17

"subscription_id": "some-id-2",

_17

"topic": "events",

_17

"arguments": {}

_17

}

_17

]

_17

}

If there are no active subscriptions, subscriptions array will be empty.

Request fields

Name	Type	Required	Description
action	STRING	YES	Action to perform. Must be list_subscriptions to initiate a list subscription request