Webhooks

Server event subscriptions

bg-dots
bg-dots

The System → Webhooks section sends HTTP notifications to an external system when selected server events occur (accounts, conferences, participants, recording, and others). The page has two tabs: “Webhooks” (subscribers and log) and “Webhook Settings” (automatic log cleanup).

Webhooks

  • “New webhook” – add a subscriber (URL and event list).
  • “Restart service” – restarts the delivery service; the subscribers list is unchanged.
  • “Purge events older than a day” – manually deletes event log records older than 24 hours.

Webhook subscribers

When there are no subscribers, the table is empty. After a subscriber is added, rows show delivery statistics.

  • “URL” – address that receives the event POST.
  • “Last sent event” – type and time of the last successful delivery.
  • “Average ping” – average response time of the URL.
  • “Success rate” – number of successful deliveries.
  • “Error rate” – number of failed attempts.
  • “Total sent” – successful plus failed sends.
  • “Actions” – edit or delete the subscriber.

Webhook event log tail

A short log of what the service tried to send.

  • “#” – record number.
  • “Timestamp” – date and time.
  • “Type” – event type.
  • “Payload” – notification body.

Add a subscriber

Use “New webhook”. Dialog title: “Add a new webhook subscriber”.

  • “Callback URL” – where to send events. HTTPS to a public address is expected by default. Specify a port only if it is non-default (443 / 80 need not be written).
  • “Allow an insecure HTTP connection” – allow delivery over HTTP without TLS.
  • “Allow access to private networks” – allow URLs on the internal network (otherwise such addresses are rejected).
  • “Authorization type” – how the server authenticates to the URL: “None”, “HTTP Basic”, “Bearer token”. Basic / Bearer show credential fields.
  • “Subscribe to events” – which events to send. * — all; a pattern such as conference.* — a group; individual codes — one event (conference.started, participant.connected, recording.completed, and others from the form list).
  • “Cancel” – close without creating.
  • “Add” – create the subscriber.

Step 1. Open System → Webhooks, “Webhooks” tab.
Step 2. Click “New webhook”.
Step 3. Enter the URL; enable HTTP and/or private networks if needed.
Step 4. Choose authorization type and mark events.
Step 5. Click “Add”.

Webhook Settings

  • “Enable automatic deletion of events older than a day” – once a day, purge log records older than 24 hours. If off, cleanup is only via “Purge events older than a day” on the “Webhooks” tab.
  • “Save” – save the setting.

Step 1. Open “Webhook Settings”.
Step 2. Enable automatic cleanup.
Step 3. Click “Save”.

E-Mail settings Oauth 2.0