Integrations

ClaimVyne connects to the systems your claims operation already runs on.

No rip-and-replace. No parallel stack. ClaimVyne fits into your existing Guidewire, Majesco, or Duck Creek environment — and extends into your estimating platforms, data services, and compliance workflows.

Claims Management Systems

Core CMS Integrations

ClaimVyne operates as a triage layer on top of your existing CMS — not a replacement. Claims are created, enriched, and routed in your system of record.

Guidewire ClaimCenter

Bi-directional API integration. ClaimVyne reads FNOLs from ClaimCenter queues and writes back enriched claim data, coverage confirmation, severity scores, and routing assignments.

Native API

Majesco ClaimVantage

REST API integration with ClaimVantage workflows. FNOLs trigger ClaimVyne pipeline automatically via webhook — no manual queue checks required.

REST API

Duck Creek Claims

Duck Creek event-driven integration. ClaimVyne subscribes to FNOL submission events and returns enriched claim objects — with coverage, severity, and assignment data — within minutes.

Event-driven

Custom PAS / CMS via API

Running a proprietary or legacy CMS? ClaimVyne's open API allows integration with any system that can send and receive JSON over HTTPS — with configurable field mapping.

Open API

Claims Data Services

Data Services and Verification

ISO ClaimSearch

Automatic ClaimSearch submission at FNOL intake — returning prior claim matches, claimant history, and fraud indicator flags before the claim enters an adjuster queue.

CCC One / Solera AudaExplore

Auto claims route directly to CCC or Solera with VIN, loss type, and claimant contact pre-populated — eliminating manual data reentry into the estimating platform.

Xactimate / Symbility

Property claims push to Xactimate and Symbility at adjuster assignment — with structured loss data, location, coverage limits, and claimant contact pre-populated in the estimate file.

Infrastructure and Compliance

Compliance and Operations Infrastructure

Email FNOL Intake (Microsoft 365 / Google Workspace)

ClaimVyne reads FNOL emails from your claims inbox — Microsoft 365 or Google Workspace — via OAuth-secured connection. No forwarding rules or mailbox permissions required.

EDI 278 / 837 / ISO Standards

Standard EDI transaction sets for insurance claims — including ISO 278, 837, and ClaimSearch — are parsed natively without additional transformation or mapping effort.

SFTP / Secure File Transfer

For carriers using batch FNOL file delivery from TPAs, ClaimVyne supports SFTP ingestion of structured and semi-structured files with configurable field mappings.

API-First Architecture

Everything ClaimVyne does is available as an API.

ClaimVyne's pipeline — FNOL parsing, coverage confirmation, severity scoring, routing — is fully accessible via REST API. Carriers with custom CMS environments or internal engineering teams can integrate at the API level rather than using a pre-built connector.

Full API documentation is available to pilot customers. We provide sandbox credentials for integration testing before production deployment.

REST / HTTPS JSON payloads OAuth 2.0 auth Sandbox environment Webhook events

POST /v1/fnol/process

Content-Type: application/json
Authorization: Bearer {api_key}

{
  "claim_id": "CLM-2026-004821",
  "lob": "auto",
  "fnol_text": "Claimant reports collision...",
  "policy_number": "POL-CT-881204"
}

→ 200 OK — {
    "severity_score": 6.4,
    "reserve_estimate": 18000,
    "adjuster_assigned": "adj_007",
    "flags": ["subrogation_possible"]
  }

Integration questions?

Bring your stack. We'll map the integration before the pilot begins.

Every pilot engagement starts with a technical integration assessment — so we understand your CMS, PAS, and data services environment before we run a single claim.

Request a Pilot Security Overview