Skip to main content
POST
Partner - Store secure encrypted data

Authorizations

Authorization
string
header
required

Bearer token authentication. Can be either a JWT token or API key.

Headers

Authorization
string
required

Bearer token for authentication. Can be either a JWT token or API key.

Body

application/json

Secure data and metadata

public_key
string
required

Public key in hex format used to encrypt the data

Required string length: 32 - 4096
Pattern: ^[0-9a-fA-F]+$
checksum
string
required

SHA-256 checksum of the original plaintext for verification (required for partner endpoint)

Pattern: ^[a-fA-F0-9]{64}$
data
file
required

Base64-encoded encrypted data

padding_type
enum<string>
default:OAEP

Padding type used for encryption

Available options:
OAEP
metadata
object

Optional metadata about the data

Response

Secure data successfully stored

backup_id
string<uuid>

Unique identifier for the stored backup

checksum
string

SHA-256 checksum that was verified

data_size
integer

Size of the encrypted data in bytes

backup_type
enum<string>

Type of backup (always 'data' for secure-data endpoint)

Available options:
data
metadata
object

Combined metadata including original metadata