Webhook Configuration

Event-Driven Integrations

Webhooks allow C2MS to push real-time notifications to your external systems whenever specific events occur on the platform. Instead of polling the API for changes, your application receives an HTTP POST request containing the event payload as soon as the event happens. This enables responsive integrations such as syncing claim updates to a CRM, triggering accounting entries on policy binding, or alerting external monitoring systems.

Supported Events

• policy.created, policy.updated, policy.cancelled — lifecycle events for policy records

• claim.opened, claim.reserved, claim.settled, claim.closed — claims workflow events

• quote.generated, quote.accepted, quote.expired — quote lifecycle events

• payment.received, payment.failed — financial transaction events

• user.created, user.deactivated — user management events

Payload Structure and Security

Each webhook delivery includes a JSON payload containing the event type, timestamp, affected resource ID, and a snapshot of the changed data. Payloads are signed with an HMAC-SHA256 signature using your webhook secret key, which you should verify on receipt to ensure the request originated from C2MS. Failed deliveries are retried up to five times with exponential backoff.

Configure webhooks from Settings > Integrations > Webhooks. You can create multiple webhook endpoints, each subscribed to different event types. The webhook management interface includes a delivery log showing recent payloads, response codes, and retry status for troubleshooting.