Image Hosting

Image hosting: upload an image (or a video up to 10 seconds) and get a directly linkable CDN address, with options for output format, encryption and storage location. 2 channels are currently available.

/api/ImageHosting/

Service Description

The image hosting service uploads images to third-party hosting platforms and returns CDN direct links, ideal for site illustrations, Markdown image hosting and user avatars, with no need to run your own storage or bandwidth.

The scdn channel accepts a local image or a remote image URL, and the server de-duplicates by SHA-256 content hash, so uploading the same image again returns the existing link without consuming extra capacity. The picui channel adds server-side Token-pool management: view used and remaining capacity per Token, and top up Tokens in bulk.

Both channels require project signature authentication. Link availability on third-party hosts is up to them, so keep the original files for anything important.

scdn.io Image Host

scdn.io (img.scdn.io) image hosting Signature Required

Uploads an image and returns a link; the server deduplicates by SHA-256 and returns the existing link for duplicate images. Requires a project signature.

POST /api/ImageHosting/scdn/upload Total calls: 0

Upload Image

Upload an image and get a directly usable CDN link.

Image file

Local image file (multipart field image; supports jpg/png/webp/gif/bmp/tiff); choose either this or image_url

Remote Image URL

Remote image address (http/https), fetched by the server; choose either this or image

Output Format

Optional: output format, default auto

CDN Domain

Optional: specify the CDN domain for the links (e.g. img.scdn.io); leave empty to choose automatically

Storage Location

Optional: storage location

Enable Password

Optional: encrypted upload (encrypted images never take part in deduplication)

Access Password

Optional: required when password_enabled=true

Password Mode

Optional: password mode, default plain

Issue Text

Optional: required when password_type=qa

The request body is multipart/form-data (file field image; use the file picker below to upload directly); when using image_url you may also use application/x-www-form-urlencoded.
data contains url / filename / storage_backend / compression stats / deduped (whether the image was deduplicated) / password_protected.
The server deduplicates by SHA-256: on a hit the message reports that the image already exists and was deduplicated, and deduped=true.
This service requires a project signature (app_id/timestamp/nonce/sign); the online debugger signs automatically on the server side.

PicUI Image Host

PicUI (v2.picui.cn) image hosting Signature Required

Uploads an image and returns a link; the PicUI account Token is held and accounted for by the server-side Token pool, switching automatically when capacity runs out, so the caller needs no account. Requires a project signature.

POST /api/ImageHosting/picui/upload Total calls: 1

Upload Image

Upload an image and get a directly usable link (with html / markdown and other reference formats).

Image file *

Local image file (multipart field image), required

Image Permission

Optional: image permission; leave empty to use the PicUI default

Storage Strategy ID

Optional: PicUI storage strategy ID, default 1 (the regular user strategy)

Album ID

Optional: target album ID

Expiry Time

Optional: image expiry time, format yyyy-MM-dd HH:mm:ss

Temporary Upload Token

Optional: PicUI temporary upload Token (its token field); usually not passed

The request body is multipart/form-data (file field image; use the file picker below to upload directly).
The PicUI account Token is selected automatically from the server-side Token pool, so the caller neither needs nor is able to specify it; after a successful upload the Token capacity is decremented by the image size returned by PicUI, and once the capacity is exhausted the Token is deleted automatically and the next one is used.
data contains url / size_kb / size_bytes / mimetype / extension / md5 / sha1 / links (html, bbcode, markdown, markdown_with_link, thumbnail_url, etc.).
Pool alert: after an upload, if the remaining pool capacity drops below 50MB the system automatically sends one restock reminder to the admin mailbox (environment variable QQ_MAIL_ACCOUNT; nothing is sent if it is not configured). The alert is sent only on the crossing itself, and fires again only after the pool is restocked above 50MB and drops below again.
Returns 50002 when the Token pool is empty or all capacities are exhausted; call the Import Tokens endpoint first.
This service requires a project signature (app_id/timestamp/nonce/sign); the online debugger signs automatically on the server side.

GET /api/ImageHosting/picui/tokens Total calls: 3

Query Token Pool

View the overall pool capacity plus the used / remaining capacity of each Token (Tokens are masked).

data top-level fields:
count: number of usable Tokens currently in the pool
total_capacity_mb: total capacity of all Tokens (MB)
total_used_mb: total used capacity of all Tokens (MB)
total_remaining_mb: total remaining capacity of all Tokens (MB) — how much you can still upload; use this field to decide whether to restock
total_capacity_bytes / total_used_bytes / total_remaining_bytes: byte values corresponding one-to-one to the three fields above, for precise computation in code
items: details of each Token in the pool, with these fields:
items[].token: masked Token value (first 6 and last 4 characters kept, e.g. 657|uN****afdb)
items[].capacity_mb / items[].capacity_bytes: total capacity of the Token
items[].used_mb / items[].used_bytes: used capacity of the Token
items[].remaining_mb / items[].remaining_bytes: remaining capacity of the Token (= capacity minus used, minimum 0)
items[].create_time: when the Token was added
Units: capacity is provided both in MB (2 decimal places, easy to read) and in bytes (easy to compute).
Tokens whose capacity is exhausted (used ≥ capacity) are deleted automatically, so every Token listed in items can still be used; the server only keeps capacity records and never stores images.

POST /api/ImageHosting/picui/tokens Total calls: 3

Import Tokens

Add one or more Tokens to the pool (enter them directly, or upload a file with one Token per line).

Token

Optional: Tokens to add, several allowed (provide at least one of this and token_file)

Multiple values: Repeatable; or separate several values with commas or newlines to submit them at once

Token File

Optional: text file with one Token per line (UTF-8)

Capacity per Token (MB)

Optional: capacity of each Token (MB), default 50

Tokens are unique: the same Token is stored only once, so repeated imports create no duplicates (those already in the database, or repeated within the same request, are counted in duplicated and skipped).
tokens supports repeated fields and comma- or newline-separated values, so several Tokens can be submitted at once; Tokens must not contain whitespace such as spaces (files with comments or extra columns are rejected to avoid importing invalid Tokens).
token_file is a text file with one Token per line; it can be used together with tokens.
data fields: submitted = number of Tokens submitted (after splitting by line/comma and deduplicating); created = number actually added; duplicated = number skipped as already existing; duplicated_tokens = masked list of skipped Tokens; capacity_bytes / capacity_mb = capacity of each new Token.
Up to 1000 Tokens per import; this service requires a project signature (app_id/timestamp/nonce/sign).