All committers have signed the CLA.

Don't forget to update the Dockhand manual.
Dunno if the reference to bark can be added as link/reference to https://github.com/Finb/Bark.

Suggestion: add the link https://github.com/Finb/Bark to the comments in the code as well? File: src/lib/server/notifications.ts line 445?

Don't forget to update the Dockhand manual.

@radoeka Could you tell me where the document repository is? I can't find it. I've tried searching within this project, on the Finsys homepage, and even globally on GitHub. 😅

I can't :( I assume it is an in house/private repository.
Perhaps mention the parts that should get an update, but I think I provided these above already.

Question: would you be able to implement #1099 (Apprise Signal Messenger Integration) too (it is using a rest api)?

@undirectlookable thanks, goes out in 1.0.32

@radoeka i will update the manual and implement Signal in #1099

A few small follow-ups I layered on top so it covers the common Apprise/Bark patterns end to end:

• Multi-device — bark://host/k1/k2/k3 now works and posts to Bark's device_keys batch field. Matches what Apprise users coming from the upstream bark:// scheme expect.
• Query params — ?sound=, ?level=, ?group=, ?icon=, ?url=, ?badge=, ?copy=, ?volume=, ?ttl=, ?call=, ?autoCopy=, ?isArchive=, ?action=, ?subtitle=, ?category=. Numeric ones get parsed; the rest pass through verbatim.
• Level mapping — info → active, warning → timeSensitive, error → critical by default; explicit ?level= in the URL still wins.
• Response check — Bark returns HTTP 200 even when code != 200 (e.g. invalid device key). Added the JSON parse so wrong keys actually surface as failures.

Manual section updated too with the URL formats + a small table for the Bark-specific query params.

Crediting you in the v1.0.33 changelog entry. Thanks again!