Lsky Pro / Chevereto

Engine: multipart/form-data · Preset: Lsky Pro / Chevereto

Both are self-hosted image galleries with a token-authenticated upload API. The preset targets Lsky Pro v2's API shape; Chevereto is close enough that the same profile works with one field changed, noted below.

Configuration — Lsky Pro#

Settings → Hosts → + → Lsky Pro / Chevereto.

The Accept: application/json header is not optional. Without it Lsky Pro answers with an HTML error page on failure, and Dropline reports The response is not valid JSON instead of the real problem.

Get a token#

Either from the web UI — sign in, then Settings → API tokens (接口 Token) — or from the API:

curl -sS -X POST https://your-domain.com/api/v1/tokens \
     -H "Accept: application/json" \
     -F "email=you@example.com" \
     -F "password=your-password"

The response's data.token looks like 1|xxxxxxxx…. Paste it whole; the leading 1| is part of the token.

Optional extra form fields#

Lsky Pro accepts more parameters, and Dropline's Extra form fields sends them alongside the file:

Values are templated, so expired_at can be built from {{date}} if you want.

The response#

{
  "status": true,
  "message": "上传成功",
  "data": {
    "key": "abc123",
    "name": "a1f3c9.png",
    "links": {
      "url": "https://your-domain.com/i/2026/08/19/a1f3c9.png",
      "html": "<img src=\"…\" alt=\"…\" />",
      "markdown": "![](…)"
    }
  }
}

data.links.url is the direct link. data.links.markdown is also there, but prefer Dropline's own Copy as Markdown setting — it uses the original filename as the alt text.

Configuration — Chevereto#

Chevereto's v1 API differs in two fields:

Chevereto's own key is passed as ?key=… rather than as a Bearer header. Its response is shaped like:

{
  "status_code": 200,
  "image": {
    "url": "https://your-domain.com/images/2026/08/19/abc.png",
    "display_url": "https://your-domain.com/images/2026/08/19/abc.md.png"
  }
}

Set the JSON path to image.url for the original, or image.display_url for the resized variant.

Object key template#

Both services rename uploads according to their own settings, so the key template does not control the final path. Leave the default.

Common problems#