Every request needs an API key, issued by the bot owner via the Telegram bot's /createkey command. Send it as an X-API-Key header (a Bearer Authorization header also works).

Upload a file

POST  /api/v1/upload

curl -X POST https://dogbox.my.id/api/v1/upload \
  -H "X-API-Key: YOUR_KEY" \
  -F "file=@photo.jpg"

Returns the new file’s id, public link, name, and size.

List your files

GET  /api/v1/files?page=1&limit=20

curl https://dogbox.my.id/api/v1/files \
  -H "X-API-Key: YOUR_KEY"

File info

GET  /api/v1/info/:id

curl https://dogbox.my.id/api/v1/info/abc123 \
  -H "X-API-Key: YOUR_KEY"

Delete a file

DELETE  /api/v1/file/:id

curl -X DELETE https://dogbox.my.id/api/v1/file/abc123 \
  -H "X-API-Key: YOUR_KEY"

Your key info

GET  /api/v1/me

curl https://dogbox.my.id/api/v1/me \
  -H "X-API-Key: YOUR_KEY"

Limits

Note: on a Vercel deployment specifically, /api/v1/uploadis limited by Vercel’s own ~4.5MB function request-body size — the web upload form isn’t affected since it uploads directly to Blob storage from the browser. A VPS deployment has no such cap on the API endpoint.