Skip to main content
All endpoints return the following response headers:
  • X-Id — The node’s public key identifier
  • X-Session-Token — The current cluster session token
  • Request-Signature — Cryptographic signature of the response for verification

​
GET /cluster/info

Returns the list of all peers currently known to this node in the cluster, along with their state and connection details. 
curl https://<node-host>:9000/cluster/info
Response 200 OK Returns an array of Peer objects.
​
[]
array
Array of peer objects
Example response: 
[
  {
    "id": "c7f9a08bdea7ff5f51c8af16e223a1d751bac9c541125d9aef5658e9b7597aee",
    "ip": "13.56.42.10",
    "publicPort": 9000,
    "p2pPort": 9001,
    "session": "20180203073000",
    "state": "Ready"
  }
]

​
GET /cluster/session

Returns the current cluster session token. The session token changes when the cluster re-forms. Returns 404 if no active session exists. 
curl https://<node-host>:9000/cluster/session
Response 200 OK
​
token
string
The current cluster session token (formatted as a timestamp integer, e.g. 20180203073000)
Response 404 Not Found No active cluster session exists. The node may still be initializing. Example response: 
{
  "token": "20180203073000"
}

Build docs developers (and LLMs) love

Get started for freeTalk to us