Key Custody

Share refresh, phase 1 done

The vault stores its new share for the next generation as pending. Nothing live changes: the old shares, wraps and kit keep working until commit. Next, wrap the new device share for generation (PUT client-share with generation), seal and save a new kit, then commit.

post/v1/keys/{key_id}/tss/refresh/complete

Request

  • Base URL: https://api.1claw.co
  • URL: https://api.1claw.co/v1/keys/{key_id}/tss/refresh/complete
  • Auth: HTTP bearer

Path parameters

key_idstring uuid required

Request body

session_idstring uuid required
client_round2string required
recovery_round2string required

Response

Pending

key_idstring uuid
generationinteger
public_key_packagestring

Changes

No recorded changes to this operation across all 1 revision of this API.