Core claims systems integration
Ishqkala + Snapsheet Claims
Real-time subrogation signals from Snapsheet Claims event webhooks and APIs.
Overview
Snapsheet Claims is a cloud-native claims platform used by carriers, MGAs, TPAs and fleet operators. Snapsheet pushes claim milestones, such as a status change, a tag added, an estimate approved or a task assigned, to external systems through event webhooks, and provides APIs to customers under its commercial agreements. Ishqkala subscribes to those events, pulls claim detail with credentials your Snapsheet account issues, and returns findings as a task, a note or a tag your team defines.
Use cases
- Flag rear-end and intersection collisions the moment the first estimate is approved.
- Identify commercial fleet and rideshare vehicles as adverse parties from notes and photos.
- Trigger early evidence preservation requests on high-value claims before vehicles are repaired or salvaged.
- Tag subrogation candidates so your existing Snapsheet workflows route them without manual review.
Architecture & data flow
How data moves between Snapsheet Claims and Ishqkala.
01
Event received
Snapsheet sends a webhook when a claim milestone occurs, such as an estimate approval or status change.
02
Claim fetch
Ishqkala calls the Snapsheet APIs for notes, parties, documents and estimates on that claim.
03
NLP
Notes, statements and police reports are read for fault signals such as a rear-end impact or a citation issued.
04
Scoring
The claim is scored on recoverable dollars, win probability and days until SOL expiry.
05
Write-back
Qualifying claims receive a task, a finding note and the subrogation tag, usually within minutes of the event.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Claim | Read | Loss date, loss location, line, status and assignment, used to set the SOL clock and route findings. |
| Parties and vehicles | Read | Insured, claimant and other driver details with vehicle information, used to name the adverse party. |
| Notes | Read / write | Handler notes parsed for liability language; Ishqkala adds a finding note with the cited text. |
| Documents and photos | Read | Police reports, statements and damage photos attached to the claim. |
| Estimates | Read | Approved estimates and supplements, including virtual appraisal estimates, used for the damages figure. |
| Task | Write | A subrogation review task assigned to the right handler or queue. |
| Tag | Write | A subrogation candidate tag your team defines, which your existing Snapsheet workflows can act on. |
Security & data governance
Controls on this connection.
- Webhook endpoint secured with TLS 1.3 and request verification; events that fail verification are dropped and logged.
- API credentials scoped by your Snapsheet administrators and stored in an encrypted secrets vault.
- AES-256 at rest in US AWS regions only, with AWS GovCloud available.
- Zero model training on your claim files.
- Audit log of every event received and every write-back made.
Setup timeline
From kickoff to first findings.
Week 1
Credentials and webhooks
Your Snapsheet administrators issue API credentials and point the relevant event webhooks at Ishqkala.
Week 2
Mapping
Map claim types, statuses and tags; agree task routing and the subrogation tag name.
Weeks 3 to 4
UAT
Handlers review findings in a test environment and set score thresholds.
Week 5
Go-live
Production webhooks enabled; a historical export is swept in parallel.
FAQ
Snapsheet Claims integration FAQ
No. Your Snapsheet administrators enable webhooks and issue API credentials under your existing agreement. Ishqkala is not presented as a certified Snapsheet partner.
Status changes, estimate approvals and new documents. Those are the moments when liability evidence usually lands on the claim.
No. Your Snapsheet workflows keep managing the recovery. Ishqkala adds note- and document-level liability detection and SOL tracking that feed those workflows.
No. Ishqkala never contacts adverse parties. Your handlers decide whether to pursue and send every demand.
More core claims systems
Find the millions hiding in your closed claim files before the Statute of Limitations expires.
We'll scan a batch of 500 closed claims for free and deliver an itemized recovery manifest within 5 business days.