lacuna API
Upload screenshots, videos and notes from your scripts, programs or your own server, and get a link you control: access, password, expiry and a view limit.
Address and format
Every method works over HTTPS at https://lac.pics/api/v1. Requests and responses are JSON in UTF-8; files are uploaded as multipart/form-data.
Every response carries an X-Request-ID header. If something goes wrong, send it to support: it identifies the request.
First request
- Create a key in your console under API. The full key is shown once: keep it like a password.
- Check the key: the response returns your account, limits and the key itself.
curl "https://lac.pics/api/v1/account" \
-H "Authorization: Bearer lac_api_YOUR_KEY"- Upload a file: the response contains its link,
url.
curl -X POST "https://lac.pics/api/v1/uploads" \
-H "Authorization: Bearer lac_api_YOUR_KEY" \
-H "Idempotency-Key: capture-2026-09-27-a7f3c1" \
-F "file=@capture.png" \
-F "visibility=unlisted"Guides
- Authentication and keysEvery request is signed with an API key in the Authorization header. A key works only with its own account’s files and only within its permissions.
- Uploading filesOne request for screenshots and short videos; parts for large files and unstable networks. A file has its link right after the upload.
- Links and accessEvery file and note has its own link. You decide who opens it and for how long: access, password, one-time opening, expiry and a view limit.
- NotesA note is text, Markdown or highlighted code behind its own link. Access, password and expiry work like for files.
- ErrorsAn error is JSON with the HTTP status, a machine-readable code and a message. Make decisions in your code by code: it is stable, while messages may change.
- LimitsLimits apply per account: all its keys share one budget. GET /api/v1/account returns the exact numbers of your plan in limits.
- Windows app and device keyThe lacuna app for Windows connects to your account through the browser and gets a key of its own, the device key. There is no need to create a key by hand.
OpenAPI specification
These pages are built from the OpenAPI 3.0 specification when the site is built, so they match the API. The full specification file (JSON) downloads after you sign in; it also lists the methods that work only from the console.