Developer

Webhooks & Event Streams

Subscribe to real-time events from Regure and push data to external systems. Sync to data warehouses, trigger notifications, update BI tools, and send audit events to SIEM systems automatically.

Request Webhook Access →API Documentation

Real-time event notifications for insurance workflows

Webhooks allow you to subscribe to events in Regure and receive real-time HTTP notifications when those events occur. When a document is uploaded, a claim status changes, or a workflow completes, Regure sends an HTTP POST request to your configured endpoint with event data in JSON format.

Webhooks are essential for building real-time integrations with external systems. Instead of polling Regure's API repeatedly to check for changes (inefficient and slow), your systems receive instant notifications when events occur. Use webhooks to sync data to warehouses, trigger automated actions in other systems, send notifications to team communication tools, or feed real-time dashboards.

Regure's webhook infrastructure is designed for reliability — automatic retries with exponential backoff, delivery confirmation, and failure notifications. Configure webhook signatures to verify event authenticity. Monitor webhook health and delivery success rates from your Regure dashboard.

Webhooks are included with all Regure plans. No additional cost for webhook delivery volume. Enterprise accounts can configure multiple webhook endpoints for different event types or environments (development, staging, production).

Real-Time DeliveryHTTP POST to your endpoint within seconds of event occurring

Automatic RetriesFailed deliveries retry with exponential backoff for up to 24 hours

HMAC SignaturesVerify event authenticity with HMAC-SHA256 webhook signatures

Event Types

Available webhook events

Subscribe to specific event types or receive all events. Filter by event type, claim ID, document type, or user.

Document Events

document.uploaded — Document uploaded to Regure from any source
document.classified — AI classification completed with confidence score
document.extracted — Field extraction completed, extracted data available
document.deleted — Document deleted by user or retention policy

Claim Events

claim.created — New claim created in Regure
claim.updated — Claim status, assignment, or data updated
claim.completed — Claim closed or settled
claim.note_added — Note or comment added to claim

Workflow Events

workflow.started — Workflow instance initiated
workflow.step_completed — Individual workflow step completed
workflow.completed — Entire workflow completed successfully
workflow.failed — Workflow failed or encountered error

User Events

user.login — User logged into Regure (for audit logging)
user.document_accessed — User accessed or downloaded document
user.permission_changed — User role or permissions modified

Setup

How to configure webhooks

Configure webhooks from your Regure dashboard or via API. Test delivery before going live.

Provide Endpoint URL

Specify the HTTPS URL where you want to receive webhook events. Regure will POST JSON payloads to this endpoint when events occur. Endpoint must accept POST requests and return HTTP 200-299 status codes to confirm receipt.

Select Event Types

Choose which event types to receive. Subscribe to specific events (e.g., only claim.completed) or receive all events. Configure separate endpoints for different event types (e.g., send document events to one endpoint, claim events to another).

Configure Authentication

Regure signs all webhook payloads with HMAC-SHA256 signatures using a shared secret. Verify signatures in your endpoint code to ensure events are from Regure. Optional: configure custom HTTP headers (e.g., Authorization header) if your endpoint requires additional authentication.

Test Delivery

Send test events from Regure dashboard to verify your endpoint receives and processes events correctly. Monitor delivery success rate and response times. Enable webhook logging in Regure to debug delivery failures. Go live after successful testing.

Payload Structure

Webhook payload format and examples

All webhook payloads are JSON with consistent structure: event metadata, event type, and data snapshot.

Example: document.classified event

Payload sent when a document is classified by Regure's AI engine.

{
  "event_id": "evt_abc123xyz",
  "event_type": "document.classified",
  "created_at": "2024-02-18T14:30:22Z",
  "data": {
    "document_id": "doc_def456",
    "filename": "police_report_claim_2847.pdf",
    "claim_id": "CLM-2024-001",
    "classification": "police_report",
    "confidence": 0.987,
    "uploaded_by": "user_789",
    "uploaded_at": "2024-02-18T14:28:15Z",
    "source": "email",
    "file_size_bytes": 245678
  }
}

Example: claim.completed event

Payload sent when a claim is closed or settled.

{
  "event_id": "evt_xyz789abc",
  "event_type": "claim.completed",
  "created_at": "2024-02-18T16:45:33Z",
  "data": {
    "claim_id": "CLM-2024-001",
    "claim_number": "CLM-2024-001",
    "policy_number": "POL-2024-5678",
    "claimant_name": "John Smith",
    "loss_date": "2024-02-15",
    "loss_type": "auto_accident",
    "status": "settled",
    "settlement_amount": 5200.00,
    "assigned_adjuster": "adjuster_456",
    "created_at": "2024-02-18T10:15:00Z",
    "completed_at": "2024-02-18T16:45:33Z",
    "cycle_time_hours": 150.5
  }
}

Example: workflow.completed event

Payload sent when a workflow completes successfully.

{
  "event_id": "evt_mno456pqr",
  "event_type": "workflow.completed",
  "created_at": "2024-02-18T15:22:18Z",
  "data": {
    "workflow_id": "wf_123",
    "workflow_name": "FNOL Intake and Routing",
    "instance_id": "wfi_789",
    "claim_id": "CLM-2024-001",
    "started_at": "2024-02-18T10:15:00Z",
    "completed_at": "2024-02-18T15:22:18Z",
    "duration_seconds": 18438,
    "steps_completed": 8,
    "final_status": "success",
    "output_data": {
      "adjuster_assigned": "adjuster_456",
      "documents_processed": 5,
      "extracted_fields": 23
    }
  }
}

Use Cases

How to use Regure webhooks

Four common deployment patterns for real-time integrations.

Data Warehouse Sync

Push claim completions and document processing events to Snowflake, BigQuery, or Redshift for analytics. When a claim closes, webhook sends complete claim data to your data pipeline. Build BI dashboards with real-time claims data without batch ETL jobs.

Real-time data sync eliminates batch ETL delays

Team Notifications

Send Slack or Microsoft Teams notifications when high-value claims are created, claims exceed SLA thresholds, or workflows fail. Subscribe to claim.created events, filter by estimated damage amount, and post to Slack channel for immediate team awareness.

Alert teams to critical claims within seconds

BI Tool Syncing

Update Tableau, Power BI, or Looker dashboards in real-time as claims progress. Webhook events trigger dashboard refreshes or write directly to dashboard data sources. Executive dashboards show live claim metrics without manual data exports.

Live dashboards reflect current claim status

Compliance Logging

Send audit events (user.login, user.document_accessed, document.deleted) to SIEM systems like Splunk or LogRhythm. Meet regulatory requirements for claims file audit trails. Centralize security logs across all insurance systems.

Complete audit trails for regulatory compliance

Reliability & Security

Retry logic, failure handling, and security

Automatic Retries

If your endpoint is temporarily unavailable or returns an error status code (500-599 or timeouts), Regure automatically retries webhook delivery with exponential backoff.

Retry 1: After 1 minute
Retry 2: After 5 minutes
Retry 3: After 15 minutes
Retry 4: After 1 hour
Retry 5: After 6 hours
Final retry: After 24 hours

After 6 failed attempts over 24 hours, Regure marks the event as permanently failed and notifies your team. Failed events are logged in your Regure dashboard for manual review and retry.

Security Best Practices

Verify all webhook events are from Regure using HMAC signatures. Each webhook payload includes a signature in the X-Regure-Signature header.

Example signature verification (Node.js):

const crypto = require('crypto');

function verifyWebhook(payload, signature, secret) {
  const hmac = crypto.createHmac('sha256', secret);
  hmac.update(JSON.stringify(payload));
  const computed = hmac.digest('hex');
  return computed === signature;
}

HTTPS required for all webhook endpoints
Optional IP whitelisting (Regure webhook IPs provided)
HMAC-SHA256 signatures for event verification

FAQ

Common questions about webhooks

What happens if my endpoint is down?

Regure automatically retries failed webhook deliveries up to 6 times over 24 hours with exponential backoff. If all retries fail, the event is marked as permanently failed and your team is notified via email. You can manually retry failed events from the Regure dashboard.

Can I filter events before they're sent?

Yes. Configure filters when setting up your webhook subscription. Filter by event type (e.g., only claim.completed), claim attributes (e.g., settlement amount over $10,000), document types (e.g., only police reports), or user IDs (e.g., only events from specific adjusters). Filters reduce noise and webhook volume.

How do I verify events are from Regure?

Every webhook payload includes an HMAC-SHA256 signature in the X-Regure-Signature header. Compute the HMAC of the payload using your webhook secret and compare it to the signature header. If they match, the event is authentic. Always verify signatures to prevent spoofed webhook attacks.

Is there a limit to how many webhooks I can configure?

Standard accounts can configure up to 5 webhook endpoints. Enterprise accounts can configure unlimited webhook endpoints and set up separate endpoints for different environments (development, staging, production) or event types. No limits on webhook delivery volume.

Related Resources

Related Integrations

API Documentation · Salesforce · HubSpot

Ready to start using webhooks?

Request webhook access and get your endpoint configured. We'll help you set up filters, test delivery, and verify your integration is working correctly.

Request Webhook Access View API Docs