Key Custody
Add a wrap for another credential or the recovery code
Changed onSame write as PUT …/client-share, for a key that already has at least one wrap: the browser, holding the share in memory during a passkey session, re-wraps it under a newly added passkey's PRF output. Owner only. 409 if no wrap exists yet, or if a wrap for this credential and generation already exists (delete it first, with re-authentication, to replace it).
Needs X-Auth-Confirm: a single-use re-auth token from POST /v1/auth/reauth/complete with purpose tss.key.wrap_add, or the account password. Strong factor: once a passkey (usable on this domain) or TOTP is enrolled, the confirmation must use one of them and a password is refused. Without it the call answers 403.
post/v1/keys/{key_id}/client-share/rewrap
Request
- Base URL: https://api.1claw.co
- URL: https://api.1claw.co/v1/keys/{key_id}/client-share/rewrap
- Auth: HTTP bearer
Headers
X-Auth-Confirmstring required
Request body
Response
Wrap added
Changes
- breaking
added the new required
headerrequest parameterX-Auth-Confirm
- breaking