← Back to all docs

CASEpeer API

CASEpeer is a cloud case and practice management platform built for plaintiffs' personal injury law firms, covering intake, case workflow, documents, accounting, and reporting. An unofficial API lets you programmatically pull cases, leads, clients, tasks, notes, and case-status data—and push updates like new cases, leads, tasks, and notes back into CASEpeer.

By Alex KlarfeldMay 29, 2026
CASEpeer API

What is CASEpeer?

CASEpeer is a cloud-based case and practice management platform purpose-built for plaintiffs' personal injury law firms, and part of the 8am family of legal technology products. Firms use CASEpeer to capture and qualify leads, manage cases from intake through settlement, automate documents, track tasks and deadlines, run reporting, and handle client communication—from solo practitioners to large multi-office firms.

Core product areas include:

  • Case Management (case workflow, status tracking, and organization)
  • Client Intake and Lead capture (intake forms, lead qualification, marketing intake)
  • Document Automation (automated document generation and filing)
  • Accounting Hub (settlements, billing, and trust accounting via LawPay and QuickBooks)
  • Reporting and Legal AI tools (analytics, summaries, and chronologies)
  • Calendar and Deadline management (calendar rules and court-specific deadlines)

Common data entities:

  • Cases (matters), Case Types, Case Status, File Numbers
  • Leads, Intake Records, Clients, Contacts
  • Case Tasks, Case Notes, Caseworkers, Assignees
  • Calendar Events, Deadlines, Reminders
  • Documents, Medical and Billing Records, Settlements
  • Client Messages, Texts, and Case Status Updates

The CASEpeer Integration Challenge

Personal injury firms run their entire caseload through CASEpeer, but turning portal-driven workflows into API-driven automation is non-trivial:

  • No public developer API: CASEpeer exposes no documented REST API—programmatic access is limited to a Zapier app gated behind Pro and Advanced subscription tiers
  • Zapier-only surface: The available triggers and actions (new case, status change, new lead, create task/note) cover only a slice of the data your firm needs to read and write
  • Partner-gated integrations: Document, medical-records, and accounting integrations flow through named partners rather than open endpoints you can call directly
  • Authentication complexity: Web-portal login and session handling complicate headless, scheduled automation
  • Personal-injury-specific objects: Leads, case status pipelines, settlements, and lien data have firm-specific configurations that generic connectors break across
  • Deadline and calendar fidelity: Court-specific calendar rules and statute-of-limitations deadlines require precise date and reason-code handling when synced externally

How Supergood Creates CASEpeer APIs

Supergood reverse-engineers authenticated browser flows and CASEpeer's underlying surfaces to deliver a resilient, full-coverage API layer for your CASEpeer account—well beyond the limited Zapier triggers and actions.

  • Handles username/password login and MFA securely within a managed session
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across cases, leads, clients, tasks, notes, and calendar entities so you integrate once and rely on consistent objects
  • Aligns with your firm's case types, status pipelines, and custom fields to ensure accurate, compliant access

Use CASEpeer with AI agents: CASEpeer MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your case types, status pipelines, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready CASEpeer adapter tailored to your firm's configuration and data.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as CASEpeer evolves.

casepeer

API Endpoints

Authentication

POST/authenticate

Authenticate to a CASEpeer account using username/password (and MFA where enabled) and obtain a session token for downstream calls.

Cases

GET/cases

List cases with filters for case type, status, caseworker, file number, and date of injury.

Cases

POST/create_case

Create a new case with case type, client details, date of injury, and initial status.

Intake

GET/leads

Retrieve captured leads and intake records with accident type, incident date, and qualification status.

Intake

POST/create_lead

Create a new lead from a website form or marketing source with contact and accident details.

Tasks

POST/create_task

Create a case task with name, assignee, creator, and due date against an existing case.

Notes

POST/create_note

Add a case note with text linked to a specific case.

Use Cases

Sync case and status data into your warehouse

- Pull active cases, case types, and status changes from CASEpeer into a central data warehouse - Stream case-status updates to downstream BI and reporting tools - Reconcile client and contact records across systems for a unified client 360

Automate intake and lead routing

- Push website and marketing leads into CASEpeer the moment they are captured - Qualify and route new leads to the right intake staff without portal clicks - Trigger follow-up workflows when a lead converts to a signed case

Orchestrate tasks, notes, and deadlines

- Auto-create case tasks and notes from external triggers and document events - Sync court-specific deadlines and calendar rules to firm calendars - Surface overdue tasks and approaching statute-of-limitations dates to supervisors

Reconcile settlements and accounting

- Sync settlement and billing data from the Accounting Hub into general ledger and AR systems - Match LawPay and QuickBooks transactions against case financials - Surface pending disbursements and lien balances to finance workflows

Technical Specifications

Authentication

Username/password and MFA handled within a managed, encrypted session

Connectivity

Authenticated browser flows plus the CASEpeer Zapier surface where exposed by your subscription tier

Response format

Normalized JSON across cases, leads, clients, tasks, notes, and calendar objects

Rate limits

Adaptive throttling tuned to your account to avoid CASEpeer-side limits

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time pulls for cases, leads, and status changes with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for new cases, status changes, new leads, and inbound client text messages

Latency

Sub-second reads on cached entities; multi-second writes when posting cases, tasks, and notes

Throughput

Horizontally scaled workers sized to high-volume personal injury caseloads

Reliability

Retry, backoff, and idempotency keys for case, lead, and task writes

Adaptation

Continuous monitoring of CASEpeer releases and configuration drift across your firm's case types and pipelines

Frequently asked questions

CASEpeer does not publish a documented REST API; programmatic access is otherwise limited to a Zapier app available on Pro and Advanced tiers. Supergood builds a full-coverage API layer over your authenticated CASEpeer account that goes well beyond those Zapier triggers and actions.

Yes. CASEpeer's Zapier app exposes only a handful of triggers and actions. Supergood normalizes a broader set of case, lead, client, task, note, and calendar entities so you can both read and push data the native integration does not expose.

Each account is profiled against its configured case types, status pipelines, and custom fields. Supergood preserves your firm-specific values and lifecycle states rather than forcing a generic schema.

Yes. Supergood operates against your authenticated CASEpeer surfaces and runs alongside LawPay, QuickBooks, Dropbox, and other native integrations without replacing them.

Settlement, billing, and trust data managed through the Accounting Hub and partners like LawPay and QuickBooks can be surfaced through the same normalized API, alongside case and client entities.

Ready to get a real API?