Webhooks and callbacks

Incoming chat webhooks

Channel owners and administrators can create an incoming webhook with POST /v1/chat/rooms/{id}/webhooks using an authorized account. The returned URL contains a secret and is shown once. Store it on your server.

Post to that returned URL using the supported text payload:

{"text":"A deployment completed."}

The endpoint is POST /v1/hooks/{id}/{token}. Anyone holding its secret URL may post to the configured channel. Disable or regenerate the webhook if it is exposed. Channel membership and organization controls apply to management operations.

Payment callbacks

/webhooks/{gateway} is reserved for configured payment providers. Provider-specific signature verification applies. These endpoints are not general-purpose meeting hooks.

Meeting events

This FaceMeet backend does not provide a public outgoing meeting-event subscription API. Browser integrations can use the embed widget's DOM events. Internal recording-worker, conferencing, and education callbacks are service interfaces, not customer webhook subscription endpoints. Do not build an outgoing webhook consumer based on an illustrative endpoint.