Imgur

Engine: multipart/form-data · Preset: Imgur

Configuration#

Settings → Hosts → + → Imgur.

The header value is not just the id#

This is the single thing people get wrong. Imgur expects:

Authorization: Client-ID abc123def456789

So the value you paste into Dropline is Client-ID abc123def456789 — the words Client-ID, a space, then your id. Pasting the bare id gives HTTP 403.

Dropline's Custom header kind sends the value verbatim precisely so headers like this can be expressed. Do not use the Bearer kind; that is for OAuth access tokens, which are a different thing.

Get a Client-ID#

1. Sign in at imgur.com.
2. Go to api.imgur.com/oauth2/addclient.
3. Pick Anonymous usage without user authorization as the type. It asks for an authorization callback URL anyway — any URL you control is fine; it is not used.
4. Submit. Copy the Client ID. The Client Secret is not needed for anonymous uploads.

The response#

{
  "status": 200,
  "success": true,
  "data": {
    "id": "abc123",
    "link": "https://i.imgur.com/abc123.png",
    "deletehash": "xyz789",
    "type": "image/png"
  }
}

data.link is the direct image URL. data.deletehash is the only way to delete an anonymous upload later — Dropline does not keep it, so if that matters, upload under a user account through Imgur's own tools instead.

Limits and terms#

Two things worth knowing before you rely on it:

• Anonymous uploads have no owner. You cannot list, manage or recover them, and Imgur removes anonymous images that go unviewed for long periods.
• Imgur is a public gallery. Its terms prohibit using it as a general file host or a CDN for a site. For anything that is not a casual share, use object storage.

Object key template#

Imgur assigns its own id and ignores the filename, so the key template has no practical effect here.

Common problems#