Webhooks
Pragence has several webhook flows with different directions and purposes. The current CMS webhook API sends content-management events to a URL you configure. It is not a general subscription API for chat answers, connector syncs, or usage warnings.
CMS content webhooks
Create and manage CMS webhooks with the /api/v1/cms/webhooks endpoints. Use
GET /api/v1/cms/webhooks/events/supported to retrieve the event names for the
running deployment. The current event catalog includes content-entry,
publication, workflow-transition, media, and content-type changes.
The webhook can be scoped by content type and configured with a signing secret,
headers, timeout, and retry settings. Delivery records are available through
the webhook delivery endpoints. When a secret is configured, CMS deliveries
send X-Webhook-Signature: sha256=<hex>, an HMAC-SHA256 of the compact JSON
request body. Verify the exact request body using the secret configured for
that webhook. The retry delays and maximum attempts are deployment settings,
so do not assume a fixed schedule.
Other webhook flows
- Commitment handoffs: organization destinations can send explicitly accepted outcomes to a configured CRM or signed webhook. These are delivery records for business commitments, not general chat events. See Support and change management.
- Provider callbacks: payment, messaging, telephony, and email providers send inbound callbacks to provider-specific routes. Configure the exact path and signature verification for the integration in use.
The repository does not define public outbound events named
answer.completed, answer.feedback, sync.completed, document.indexed, or
quota.warning; the former generic /api/v1/webhooks subscription example and
its signature header are not a supported contract.