Skip to main content

The Case

A case is the unit of work — often a legal matter, but equally a bankruptcy estate, a compliance review, a due-diligence engagement, or any other bounded piece of work. Every case belongs to a client and has a type and a lifecycle. (In the API the underlying model is a LegalCase for historical reasons, but the endpoints and fields use "case".)

How you address it​

/cases/v1          # list, create
/cases/v1/{case}   # retrieve, update (PATCH/PUT), delete

All case endpoints are scoped. List a client's cases with filter[clientId]; see Working with Clients & Cases for the workflow.

Key fields​

FieldNotes
nameRequired; the matter's title
clientIdRequired; the client this case belongs to
caseTypeRequired; m_a, bankruptcy, litigation, compliance, due_diligence, other
caseIdDisplayHuman-facing case reference (e.g. M&A-2026-014), assigned by the system
statusLifecycle state — see below
openedAt, targetCompletionDate, closedAtKey dates
teamInternal team assignments (resolved from role assignments)
description, notes, tagsFreeform

Lifecycle​

A case's status moves through:

draft ──▶ open ──▶ on_hold ──▶ closed ──▶ archived
            ▲         │           │
            └─────────┴───────────┘   (can reopen to open)
  • draft — created but not yet active.
  • open — actively being worked.
  • on_hold — paused (e.g. awaiting a client decision).
  • closed — work finished; still visible.
  • archived — retired; soft-deleted (a DELETE archives a case).

Relationships​

  • Belongs to a client (clientId) and, through it, a tenant.
  • Carries the shared sub-resources under /entitymanagement/v1/case/{id}/….
  • Has team assignments that drive who can see and act on it (see Permissions).

See also​