pexip-event-sinks

Pexip event sinks — webhook push events

Pexip Infinity can push real-time events for conferences, participants, and call milestones to an HTTP endpoint you control. This is the push-based alternative to polling the History API — for high-volume platforms or anything approaching real-time, event sinks beat polling on latency, completeness (no 10,000-instance retention cap), and rate-limit headroom.

Why the MCP server does NOT manage event sinks. Creating or editing an event sink means telling Pexip "POST all conference and participant data to this URL." Exposing that as an LLM-callable tool is a data-exfiltration risk: a prompt-injected or confused agent could be steered into registering an attacker-controlled URL and quietly stream live meeting metadata off-platform. There is no operational reason for an agent to manage sinks — they're set up once by a human — so the server intentionally ships no *_event_sink tools, and event_sink is not in the generic-CRUD registry either. Configure sinks yourself (below); use the agent only for the reporting it enables downstream.

When to use this skill

• "Move from polling the History API to push events"
• "Set up a webhook so we get notified when calls start/end"
• "Build a CDR collector that survives the 10,000-instance retention limit"
• "Stream Pexip events into our data warehouse / SIEM / dashboard"

When NOT to use

• One-shot reads of live state → pexip-status-api / pexip-operations/live-meeting-ops.md
• Historical CDR queries / reports → pexip-history-api / pexip-operations/reporting.md

Configuring the sink (done by a human, in Pexip)

Event sinks are configured outside the MCP server, by an operator with admin access — deliberately, for the security reason above. Two supported paths:

1. Admin UI: Pexip Management Node → Platform → Event Sinks → Add Event Sink. Set the URL, protocol version (v2 is current), bulk support, TLS verification, and optional Basic-auth username/password.
2. Configuration API directly (curl / a provisioning script run by an admin, not the agent):

   POST https://<mgmt-node>/api/admin/configuration/v1/event_sink/
   { "name": "cdr-collector", "url": "https://collector.internal/pexip",
     "version": 2, "bulk_support": true, "verify_tls": true,
     "username": "pexip", "password": "<secret>" }