`POST /api/e2ee/escrow`

The blob is CLIENT-ENCRYPTED under the user's recovery password; the server only stores it and can never open it. All three routes act on the CALLER'S OWN ZID only — nobody can read or overwrite another user's escrow.


Method	`POST`
Path	`/api/e2ee/escrow`
Domain	Vault & encryption · E2ee Keys
Tier	computation (public)
Auth	`user`

Request

curl -X POST https://zeqsdk.com/api/e2ee/escrow \
  -H "Authorization: Bearer $ZEQ_KEY" \
  -H "Content-Type: application/json" \
  -d '{ }'   # request body — see description

Needs a machine key — mint one free: curl -X POST https://zeqsdk.com/api/demo-key/mint, then spin up your machine.

Generated from the node's own route registry (GET /api/endpoints) — this path is live.

Request​

Request