Configuring event sinks

Information about the current status of the Pexip Infinity platform and any conference instances currently in progress can normally be obtained using the Management status API. However, in deployments with high levels of live system monitoring activity, such as those managed by service providers, frequent polling of the Management Node via the API can cause performance issues.

To avoid this you can configure the system to automatically send details of every participant and conference management event to an external service known as an event sink. When an event occurs, the Conferencing Node sends this information using a simple POST of JSON data to the nominated event sink server.

Each system location can be configured with one or more event sinks. The same event sink can be used for more than one system location.

To add, edit or delete an event sink, go to System > Event sinks.

The available options are:

Option Description
Name The name used to refer to this event sink. Each event sink must have a unique name.
Description An optional description of this event sink.
URL The URL of the external server to which events are sent.
Version The internal Pexip protocol version supported by this event sink.
Username and Password The username and password used to authenticate to the external server when sending events. The username is case-sensitive. Leave these fields blank if authentication is not required.
Verify TLS Whether to enable TLS verification when sending events. Only valid if the URL is HTTPS.
Location The system locations in which to use this event sink.

What information is sent?

You cannot change what information is sent to an event sink.

To view what information is sent to an event sink, go to System > Event sinks and from the bottom right of the page, select View schema.

The same information can be downloaded as a Swagger or OpenAPI JSON document by selecting Download Swagger schema or Download OpenAPI schema.

You can also use a test site such as to view live event data being sent.

Note that conference start and end event times are from the Conferencing Node's perspective and not the Management Node's perspective.