API reference
Most users never interact with the API directly — the CLI handles all API communication. All endpoints require an Authorization: Bearer YOUR_API_KEY header.
/api/v1/upload-urlGet presigned upload URL
/api/v1/backups/{id}/confirmConfirm upload completed
/api/v1/backupsList backups
/api/v1/backups/{id}Get backup + download URL
/api/v1/backups/{id}Delete backup
/api/v1/accountAccount info
The upload lifecycle
- Authenticate with the source API key and request a presigned upload URL for the encrypted file.
- Upload the encrypted archive to that URL.
- Confirm its size and SHA-256 checksum with the API.
Confirmation compares the submitted metadata with the backup record. It is not an application restore test or a server-side decryption of the archive.
What belongs in API metadata
Source identity, filename, byte size, checksum, driver and status support the backup workflow. The archive encryption key is used locally and is not part of the upload or confirmation request.
Read the privacy boundary →