Lawmatics
Lawmatics is a legal CRM, client-intake and marketing-automation platform for law firms, from solo practices to multi-office firms. Its public developer surface is the Lawmatics OAuth API — a REST API of 177 operations across matters (called prospects in the API), contacts, companies, custom intake forms and form entries, custom fields, collections, pipelines, stages, practice areas, marketing sources and campaigns, events, tasks, notes, files, tags, users, time entries, expenses, invoices and transactions — plus a set of signed outbound webhooks. Access is OAuth 2.0 authorization code, gated on a Lawmatics support representative enabling developer settings on the account, and the resulting access token is non-expiring, unscoped and grants full CRUD over the firm.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Lawmatics the way a machine reads it — 37 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Lawmatics scores 52.7/100 (developing), with a separate agent-readiness read of 42/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Lawmatics's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lawmatics/"
title="Lawmatics on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lawmatics.svg"
alt="Lawmatics Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/lawmatics/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lawmatics/"
title="Lawmatics on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lawmatics/card.svg"
alt="Lawmatics Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Lawmatics
Each block below is one kind of artifact we hold for Lawmatics. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 27
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Lawmatics Addresses API
An Address belongs to a Firm, a Contact, or Company.
Lawmatics Collections API
The Collections API from Lawmatics — 4 operation(s) for collections.
Lawmatics Companies API
The Companies API from Lawmatics — 5 operation(s) for companies.
Lawmatics Contacts API
A Contact can be thought of as a collection of data about a "Person". A Contact record is the base for all Contactables (Matters, Clients, and Companies). Since Contact data ref...
Lawmatics Custom Emails API
The Custom Emails API from Lawmatics — 2 operation(s) for custom emails.
Lawmatics Custom Fields API
The Custom Fields API from Lawmatics — 2 operation(s) for custom fields.
Lawmatics Custom Forms API
NOTE: Field IDs for fields that are not considered "Standard", such as General fields, and Custom fields, are referred to by special long-form uuids that are enumerated on the A...
Lawmatics Email Addresses API
A Email Address is contact information that belongs to a Firm, Contact, or Company.
Lawmatics Email Campaign Stats API
The Email Campaign Stats API from Lawmatics — 1 operation(s) for email campaign stats.
Lawmatics Email Campaigns API
The Email Campaigns API from Lawmatics — 2 operation(s) for email campaigns.
Lawmatics Event Locations API
These are Firm related Locations (for events) that can be configured in Firm settings.
Lawmatics Event Types API
Event Types define Event defaults, and can trigger automations, for common types of Events created in Lawmatics. Configuring Calendar Availability defaults is not currently supp...
Lawmatics Events (Appointments) API
Events are also referred to in the app as "Appointments"
Lawmatics Files API
The Files API from Lawmatics — 3 operation(s) for files.
Lawmatics Folders API
The Folders API from Lawmatics — 2 operation(s) for folders.
Lawmatics Matters (Prospects) API
A Matter is a legal case, and the primary object in Lawmatics. NOTE: You may see Matters referenced as "Prospects" or "PNCs". This is for legacy reasons, and we are working to m...
Lawmatics Notes API
The Notes API from Lawmatics — 2 operation(s) for notes.
Lawmatics Payment Expenses API
The Payment Expenses API from Lawmatics — 2 operation(s) for payment expenses.
Lawmatics Payment Invoices API
The Payment Invoices API from Lawmatics — 2 operation(s) for payment invoices.
Lawmatics Payment Time Entries API
The Payment Time Entries API from Lawmatics — 2 operation(s) for payment time entries.
Lawmatics Payment Transactions API
The Payment Transactions API from Lawmatics — 2 operation(s) for payment transactions.
Lawmatics Phone Numbers API
A Phone Number is contact information that belongs to a Firm, Contact, or Company.
Lawmatics Tags API
The Tags API from Lawmatics — 4 operation(s) for tags.
Lawmatics Task Statuses API
The Task Statuses API from Lawmatics — 2 operation(s) for task statuses.
Lawmatics Tasks API
The Tasks API from Lawmatics — 6 operation(s) for tasks.
Lawmatics Timeline Activities API
The Timeline Activities API from Lawmatics — 2 operation(s) for timeline activities.
Lawmatics Users API
The Users API from Lawmatics — 3 operation(s) for users.
Scroll within the panel for all 27 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Lawmatics OAuth API v1.22.0
POSTMANPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Lawmatics Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Lawmatics Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Lawmatics Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Lawmatics Context
JSON-LDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Lawmatics — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lawmatics · machine-readable index on apis.io
This is an independent, third-party profile of Lawmatics, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.