Restore local TSS node binding

Called by the app after restoring its local TSS node files from backup. The node binding is scoped to the authenticated principal, not a specific wallet, because one app node may hold key shares for multiple vaults.

POST /api/v1/wallets/restore-node

Restore local TSS node binding

Python

import requests

url = "https://api.example.com/api/v1/wallets/restore-node"

payload = { "node_id": "<string>" }
headers = {"Content-Type": "application/json"}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

200

{
  "result": {
    "node_id": "<string>",
    "status": "active"
  },
  "success": true,
  "suggestion": "",
  "message": "",
  "meta": {
    "total": 123,
    "offset": 123,
    "limit": 123,
    "has_more": true,
    "after": "<string>",
    "before": "<string>"
  }
}

Headers

X-API-Key · string | null

Body

application/json

Request payload for restoring the current app's local TSS node binding.

node_id · string · required

The restored app TSS node id to bind to the authenticated principal.

Minimum string length: 1

Response

200

application/json

Successful Response

result · WalletRestoreNodeResponse · object · required

Current principal node binding after restore.

Show child attributes

success · boolean · default: true

suggestion · string · default: ""

message · string · default: ""

meta · PaginationMeta · object

Pagination metadata for list responses.

Supports both legacy offset-based and cursor-based pagination. Cursor fields (has_more, after, before) are populated for cursor-paginated endpoints. Legacy fields (offset, limit) are populated when the caller uses the deprecated offset parameter.

Show child attributes