Carrier Core Connectivity

Built to Integrate With Your Carrier Core

Claimflint connects natively to Guidewire ClaimCenter, Duck Creek Claims, Sapiens ClaimsPro, and Insurity ClaimXperience. REST and batch, your choice.

4
Carrier core systems integrated
<30d
Typical integration go-live
Platform Integrations

Four Native Integrations

Guidewire ClaimCenter

Native REST API with bi-directional claim status sync. Adjuster assignment push, reserve update, and FNOL file write-back. Compatible with ClaimCenter 10.x and ClaimCenter Cloud environments.

REST API Bi-directional Real-time Batch export

Duck Creek Claims

Event-driven webhook integration. FNOL push on first intake, reserve update on enrichment completion, closure trigger on settlement. Supports Duck Creek OnDemand and on-premise.

Webhooks Event-driven OnDemand On-premise

Sapiens ClaimsPro

Flat-file and REST modes supported. Policy lookup and coverage verification pull from ClaimsPro. Payment trigger and total-loss valuation write-back on closure.

REST API Flat-file Payment trigger

Insurity ClaimXperience

SOAP/REST hybrid integration. Batch FNOL feed for high-volume environments. Adjuster notes sync, DOI export, and subro initiation trigger.

SOAP/REST Batch FNOL DOI export
Architecture

How the Integrations Connect

Integration architecture showing Claimflint connecting to Guidewire, Duck Creek, Sapiens, and Insurity carrier core systems
Open API

Open API for Custom Integrations

If your carrier runs a proprietary core, an older Insurity legacy environment, or a mainframe-adjacent system, Claimflint's open REST API gives your integration team a documented path without waiting for a native connector. The same API powers all four native integrations — no separate SDK, no undocumented endpoints.

  • REST API with OpenAPI 3.0 specification — download and integrate
  • Webhook support for real-time event push (FNOL received, file enriched, claim closed)
  • Batch connector for mainframe and on-prem cores via flat-file exchange
  • OAuth 2.0 authentication, TLS 1.3 in transit, field-level encryption at rest
# Sample FNOL intake via REST API POST /v1/claims/fnol Authorization: Bearer {api_key} Content-Type: application/json { "policy_id": "P-2024-88821", "loss_type": "auto_collision", "loss_date": "2025-03-14", "claimant": { "name": "Jane Doe", "phone": "+1-860-226-9104" }, "intake_channel": "web_portal" } # Response: 201 Created { "claim_id": "CLM-2025-00441", "status": "enriching", "estimated_enrichment_ms": 1800 }
Get Connected

Talk to Our Integration Team

We'll map your current carrier core setup to a Claimflint integration path and estimate your go-live timeline — usually under 30 days.

Talk to Our Integration Team Request a Pilot