SettleSignal
Settlements Data breachConsumer refundsPrivacy & biometricsEmployment How we verify Guides Help center For business Log in See what you may be owed →

Data licensing

Settlement evidence intelligence, as data.

Published coverage and accepted official evidence are separate, queryable signals. You get a fresh settlement feed with row-level evidence status and the available field-level trail, so your product can cite provenance instead of guessing.

793 records with accepted official evidence
7,073 field-level citations
94% avg verification confidence
Sep 6, 2026 last verified

Who it's for 01

Built for products that help people claim what they're owed.

Claim-filing & consumer apps

A fresh, verified feed with deadlines, eligibility, and proof requirements, plus the official claim destinations. Route users to the right official form with confidence the details were checked against the source record.

Fintech & money-finding products

Surface "you may have money waiting" features backed by provenance, not scraped rumors. Each settlement carries the evidence trail your compliance and risk teams will ask for.

Law firms & administrators

Monitor the settlement landscape with explicit provenance: case and court details, administrator, deadlines, payment status, and whether official evidence is accepted, linked, or under review.

What you get 02

The full record, plus the evidence behind it.

Record fields

  • Claim deadline, plus exclusion and objection deadlines
  • Eligibility summary and class period
  • Proof requirement and estimated payout text
  • Case name, case number, and court
  • Settlement administrator
  • Payment-status lifecycle

Per-field provenance

  • Evidence source URL for the value
  • The exact supporting snippet from the document
  • Confidence score and verification tier
  • Verified and last-checked timestamps
  • Source-document type and content hash
The differentiator: public pages show the named authority only; the licensed API carries the available evidence trail — source links, snippets, document hashes, and the row-level accepted-evidence flag.

Sample 03

One field, with its provenance.

A single field_provenance entry from the detail endpoint. Evidence URLs are masked in this public sample; the full URLs are part of the licensed payload.

field_provenance.json
{
  "field_name": "claim_deadline",
  "value": "2026-09-01",
  "source_url": "https://…full-url-in-licensed-api…",
  "source_snippet": "Claims must be submitted by September 1, 2026 to the …",
  "confidence": 95,
  "verified_at": "2026-06-05T14:22:08+00:00",
  "last_checked_at": "2026-06-05T14:22:08+00:00",
  "document": {
    "type": "long_form_notice_pdf",
    "url": "https://…full-url-in-licensed-api…",
    "fetched_at": "2026-06-05T14:21:55+00:00",
    "content_hash": "sha256:9f2c…e1a7"
  }
}

Download sample (JSON)

Integration 04

A small, read-only API.

  • GET /api/v1/settlements/ paginated list of published records with evidence status
  • GET /api/v1/settlements/<slug>/ full record with per-field provenance
  • GET /api/v1/meta/ dataset metadata and live metrics
request.sh
curl https://settlesignal.com/api/v1/settlements/ \
  -H "Authorization: Bearer ss_live_EXAMPLEKEY"

Authenticate with an Authorization: Bearer header or X-API-Key. Create a key yourself from the API section of your free account — free tier, 600 requests/hour, revocable anytime. Higher limits and commercial terms are arranged per partner.

Tell us what you're building.

Start free in secondscreate a self-serve key for the free tier. Need higher limits, commercial terms, or the full per-field evidence trail? Tell us your use case and we'll scope access and a sample for your team.

We use this only to reply about data licensing — no marketing.