Zoom


Schemes	`zoom://`
Cargo feature	`service-zoom`
Service	https://zoom.us/
Body formats	`text` (first is the default)
Attachments	no
Title length	250 characters
Body length	3,750 characters
Body lines	unlimited
Request throttle	none
Vendor URLs accepted	yes

URL tokens

Token	Meaning	Type	Required	Default	Notes
`{token}`	Verification Token	string	yes		secret
`{webhook_id}`	Webhook ID	string	yes		secret

Query parameters

Parameter	Meaning	Type	Default	Notes
`mode`	Mode	choice	`full`	one of `simple`, `full`; `simple` sends `?format=message` with plain text
`token`	Verification Token	string		sets `{token}`

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):

zoom://abc123/xyz456
zoom://abc123/xyz456?mode=full
https://inbots.zoom.us/incoming/hook/abc123?token=xyz456
https://integrations.zoom.us/chat/webhooks/incomingwebhook/abc123?token=xyz456
zoom://myhookid/?token=override123
zoom://myhookid/mytoken/?token=override123
https://inbots.zoom.us/incoming/hook/abc-1_2/?token=xyz456&mode=simple

Rejected URLs:

zoom://abc123/xyz456?mode=invalid
https://inbots.zoom.us/incoming/hook/abc123
zoom://
zoom://:@/

Send one from the command line:

mercurio -t 'Backup' -b 'Finished in 42s' 'zoom://abc123/xyz456'

Notes

Zoom Team Chat incoming webhooks (zoom://).

POST https://integrations.zoom.us/chat/webhooks/incomingwebhook/{id} with the verification token in Authorization: either ?format=full with a JSON message card or ?format=message with the text as the body.

Differences with Apprise

Apprise posts to inbots.zoom.us/incoming/hook/{id}, while mercurio posts to the current integrations.zoom.us/chat/webhooks/incomingwebhook/{id} (?format=full; ?format=message for mode=simple); native URLs on either host are accepted.

Keyboard shortcuts