Store encrypted backup data
Stores encrypted backup data securely. Accepts multiple backup items in a single request via the backup array (limited to a maximum of 3 items). Requires a verification_id that exists in the identity_verifications table and belongs to the user associated with the organisation. Each backup item’s item_key (e.g., “seed_phrase”, “private_key”) is stored in the hot-keys database metadata as backup_item_key for recovery operations. This endpoint calls the hot-keys orchestrator partner-secure-data endpoint.
Authorizations
API key for authentication and authorization
Body
User identifier (REQUIRED)
"john.doe@example.com"
Verification ID from a previous verification. (REQUIRED) Must exist in identity_verifications table and belong to the user associated with the organisation.
"a7b8c9d0-e1f2-4345-a678-901234567890"
Public key in hexadecimal format. (REQUIRED) 32-4096 characters long.
32 - 4096^[0-9a-fA-F]+$"30820122300d06092a86486f70d..."
Array of backup items to store. (REQUIRED) Allows multiple pieces of data to be backed up in a single request. Limited to a maximum of 3 items.
1 - 3 elementsOptional metadata associated with the backup. Allows custom key-value pairs.
Response
Backup stored successfully
Type of backup. Always present. Value is always "data".
data "data"
Metadata associated with the backup (echoed from request + enhanced with system metadata such as API key info, stored_at timestamp, and backup_items_count). Always present.
Array of stored backup items. Each item contains the item_key, backup_id, checksum, and data_size.
1