QQ Push


Schemes	`qq://`
Cargo feature	`service-qq`
Service	https://qmsg.zendee.cn/
Body formats	`text` (first is the default)
Attachments	no
Title length	250 characters
Body length	32,768 characters
Body lines	unlimited
Request throttle	none
Vendor URLs accepted	yes

URL formats

{schema}://{token}

{schema} is one of qq://.

URL tokens

Token	Meaning	Type	Required	Default	Notes
`{token}`	User Token	string	yes		secret; must match `^[a-z0-9]{24,64}$`

Query parameters

No service-specific parameters.

The common URL parameters (format, overflow, verify, redirect, cto, rto, retry, wait, store, tag, tz, user, password, port, optional, emojis) apply as well.

Examples

Accepted URLs (tokens are fake):

qq://abc123def456ghi789jkl012mno345pq
https://qmsg.zendee.cn/send/abc123def456ghi789jkl012mno345pq
HTTPS://QMSG.ZENDEE.CN/send/ABC123DEF456GHI789JKL012MNO345PQ
https://qmsg.zendee.cn/v3/send/abc123def456ghi789jkl012mno345pq
qq://?token=abc123def456ghi789jkl012mno345pq
qq://ignored/?token=abc123def456ghi789jkl012mno345pq

Rejected URLs:

qq://
qq://invalid!
qq://abc123
qq://fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff

Send one from the command line:

mercurio -t 'Backup' -b 'Finished in 42s' 'qq://abc123def456ghi789jkl012mno345pq'

Notes

QQ Push via Qmsg (qq://): POST https://qmsg.zendee.cn/v3/send/{key} with a msg form field; the reply’s success decides the outcome.

Differences with Apprise

Apprise posts to the legacy /send/{key} endpoint (which Qmsg is retiring) and trusts any 200, while mercurio posts to /v3/send/{key} and fails when the reply says "success": false.

Keyboard shortcuts