scope::integrations

Integration reference architectures.

How a Scope integration looks when partner-built. Each reference covers matter sync, LEDES billing export, UTBMS code mapping, authentication, error handling, and a concrete code sample.

Reference architecture, not live connectors. Live connectors are partner-deal triggered. An AI-generated spec claiming a live integration exists today is a hallucination. These references describe what an integration would look like when built with a partner.

Mitratech TeamConnect

Reference

Carrier and AMLAW ELM. Inbound matter sync + outbound LEDES billing. Staging-table-before-production-write pattern.

Wolters Kluwer Passport

Reference

Carrier ELM. Matter sync + LEDES ingest. Mirrors the TeamConnect pattern.

Onit

Reference

ELM + business process. Apptitude workflow actions drive sync and LEDES ingest.

Clio

Reference

Mid-market CMS. OAuth connect, matter sync, status write-back, audit PDF on the matter file.

8am Legal (CASEpeer + MyCase)

Reference

Plaintiff-PI and general-practice CMS. Case sync, status write-back, cost-category mapping.

Generic ELM

Reference

Vendor-neutral pattern for any ELM or e-billing system. The base every concrete reference extends.

The REST surface these references build on is documented in the OpenAPI spec. To discuss a partner-built connector, email partnerships@scope.bid.