Skip to main content
POST
/
v1
/
secure
/
data
Store secure encrypted data
curl --request POST \
  --url https://service.uat-keys.coincover.com/v1/secure/data \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "public_key": "<string>",
  "data": "aSDinaTvuI8gbWludGxpZnk=",
  "checksum": "<string>",
  "padding_type": "OAEP",
  "metadata": {
    "description": "<string>",
    "content_type": "<string>",
    "original_filename": "<string>"
  }
}
'
{
  "backup_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "checksum": "<string>",
  "data_size": 123,
  "backup_type": "data",
  "metadata": {}
}

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]+$
​
data
file
required

Base64-encoded encrypted data

​
checksum
string

SHA-256 checksum of the original plaintext for verification (optional but recommended)

Pattern: ^[a-fA-F0-9]{64}$
​
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