unseal
user.security.unseal
Loads the caller’s master key into the KMS cache for this process. Required before any encrypted read/write (documents, files, shared vaults, flow submissions, …).
Auth
Bearer JWT required.
Input
- Tier 1 (Standard): omit
pin. The master key is protected by a platform-held secret only. - Tier 2 (Enhanced) and above:
pinis required. The PIN is combined (Shamir 2/2) with a platform secret to reconstruct the master key.
GraphQL
Tier 1:
Response
true on success. Scope error (data.user: null) on failure — the errors
array will say whether the PIN was wrong, missing, or the user has no
encrypted key material yet.
curl (Tier 2, with PIN)
Warning
The unsealed master key is held only in the server’s memory. A process restart re-seals every user; clients must be prepared to re-unseal on demand.