Dropadox API v1

Automate your cloud backups

Upload, list, and download files from scripts or backup tools. API keys use the same account storage and permissions as the dashboard.

API keys

Treat keys like passwords. Each key grants access to your files and is only displayed once.

Authentication

Send your key in the Authorization header. All automation routes are under /api/v1 and return JSON unless downloading a file.

Authorization: Bearer ddx_your_api_key

Quick start

Upload a file to the root of your account:

curl -X POST "https://dropadox.sytes.net/api/v1/files" \
  -H "Authorization: Bearer $DROPADOX_API_KEY" \
  -F "file=@./backup.zip"

Add -F "folderId=123" to upload into a folder.

Endpoints

MethodPathPurpose
GET/api/v1/storageRead used, available, and maximum storage in bytes.
GET/api/v1/foldersList folders available to the account.
POST/api/v1/foldersCreate a folder from JSON: { name, parentId? }.
GET/api/v1/files?folderId=IDList root files, or files in one folder when folderId is supplied.
POST/api/v1/filesUpload multipart field file, with optional folderId.
GET/api/v1/files/:fileIdDownload a file by ID.
DELETE/api/v1/files/:fileIdDelete a file by ID.

Simple backup flow

  1. Call GET /api/v1/folders and choose or create a destination folder.
  2. Upload each changed file with POST /api/v1/files.
  3. Store the returned file ID so you can download or remove that version later.
  4. Periodically call GET /api/v1/files?folderId=ID to verify what is stored.
curl "https://dropadox.sytes.net/api/v1/files?folderId=123" \
  -H "Authorization: Bearer $DROPADOX_API_KEY"

Errors and safety

Successful creates return 201. Invalid keys return 401, missing resources return 404, rate limits return 429, and storage-limit errors return 413. Revoke a key immediately if it is exposed.

© 2026 Dropadox. All rights reserved.