Incoming webhooks
An incoming webhook creates posts in one configured channel. Create it, choose the channel, and copy the generated URL when mob.so displays it. The URL contains its credential and is shown only when created or rotated. Send a JSONPOST request to that URL. body is required, text is accepted
as an alternative, and title is optional.
Outgoing webhooks
An outgoing webhook sends a JSONPOST request for selected mob events. It may
cover one channel or all channels in the mob.
Available events are:
post.createdpost.deletedcomment.createdcomment.deleted
Verify a delivery
mob.so includes these headers:
Build the signed value from the timestamp, a period, and the exact request body
bytes. Compute its HMAC SHA 256 digest with the endpoint secret. Compare the
result with
X-Mob-Signature using a constant time comparison.
Check the timestamp and signature before parsing the JSON body. Use the
delivery ID as the idempotency key for your endpoint.
Endpoint restrictions
Production endpoints must use HTTPS, include no URL credentials, and resolve to a public network address. mob.so does not follow redirects.Role permissions
Removing a permission removes the management access supplied by that role. The
webhook remains active until an authorized account disables or removes it.