Law Firm API Keys: Read-Only Access for Scripts, MCP Clients, and Integrations
Set up law firm API keys in MyLawyerLink: name each key, choose Read only or Read and write, copy it once, and revoke keys you no longer use.
A consultant emails the office manager on Thursday. She wants a Monday script that lists open matters, and she asks for the password so the script can sign in.
Owners, administrators, and the IT person they hire want that access without handing over a login. Law firm API keys in LawyerLink (MyLawyerLink) are the office credential for the job. Name the key, choose Read only or Read and write, copy it once, and revoke it when the work stops.
Not legal advice. Duty of confidentiality and vendor diligence remain the firm's call. A key gives the tool the same data access its scope allows. MyLawyerLink does not decide whether a script, a reporting vendor, or an AI client is an appropriate place for client information.
Decide whether the job needs a key or a person
A person who opens matters, sends texts, or approves invoices needs an account and a role. A script that calls the practice management API needs a key. When you connect AI tools to practice management, give the MCP client its own key. The office password stays with the office manager.
The key belongs to the office where you create it and reaches only that office's data. When the consultant or a staff member who held the secret leaves, revoke that key. A personal login is a separate choice under team roles and least privilege.
Create an API key in Slack & API
Owners and admins see the API Keys card. Creating a key and revoking one also require an active subscription.
Open Account settings, office section, Slack & API, at /account/settings/office/communications. The heading is Slack & API. The line under it reads "Connect Slack and manage API keys for" and then the office name. Slack alerts use the Slack card on this same page.
The card says: "Create keys for programmatic access (MCP, chatbot, scripts). Use Authorization: Bearer when calling the API. Read-only keys may only use GET; read/write keys can create and update data."
Key name is required, up to 120 characters. The placeholder is "e.g. Cursor MCP". Name the tool, such as "Monday open-matters script". Scope offers Read only and Read and write. Create API key stays disabled while the name is blank, and it reads "Creating..." while it saves.
The key is stored for the office as soon as that succeeds. A warning box reads "Your new API key (copy now โ it wonโt be shown again):" with a Copy button. The value starts with mll_ and a long random string. Send Authorization: Bearer mll_YOUR_KEY on /api/... paths.
The public reference is /docs, under the heading "API reference". Open API reference opens /docs/api. The machine-readable spec is /openapi.json.
Existing keys lists each name, a short prefix and an ellipsis, a Read only or Read/write badge, and "Last used" with a relative time, or "Never used", plus Revoke. An empty card says "No API keys yet. Create one above."
Choose Read only unless the tool must write
Leave Scope on Read only unless the tool must create or update records.
| Scope | What it may call | How MyLawyerLink checks it |
|---|---|---|
| Read only | GET only. POST, PUT, PATCH, and DELETE return 403, "Forbidden - read-only API keys may only use GET". | A read-only team member. Client, case, and calendar lists follow assignments. A key has none, so those lists can be empty. Test one GET first. |
| Read and write | GET, plus create and update where a Member is allowed. Some billing actions and team settings still return 403. | A Member on that office. Owner and Admin permissions stay with people in those roles. |
Use a read-only API key when you connect AI tools to practice management, and for any script that must not change files, time, or invoices. An MCP client or script that sends a Bearer key can call the documented API with that scope.
Use Read and write for a script the firm controls when it must change data, or when a Read only GET returns an empty client or case list and the report still needs every open matter. Keep Read and write off any AI or MCP client.
Know what a key cannot reach
The public reference documents clients, cases (including case events, documents, and notes), documents, calendar events, time entries, invoices, calls and recording metadata, reference lists such as case statuses and event types, notifications, and team details. Team details return 403 without permission to view team settings.
Law firm API keys are refused on sign-in and sign-up, on the client portal (/api/portal/*), on webhooks, on cron, and on impersonation. A team key also gets 403 on firm-wide routes (/api/firm/*), court reports, the Redwell assistant, the knowledge wiki, global search, tasks, AI document helpers (IR reports, call transcription, and proofreading), account settings and user preferences, stored Twilio or DocuSeal credentials, Zoom, Webex, and Dropbox sign-in, and A2P compliance. Deleting the office is blocked. A key cannot list keys, create a key, or revoke an API key. A signed-in person manages keys.
API key requests are rate limited. The form has no expiration date. Access ends when you revoke the key. Read only and Read and write are the only scopes. Read zero data retention and confidentiality before a live key sits in an AI tool.
Store, monitor, and revoke an API key
MyLawyerLink stores a SHA-256 hash and a short prefix (mll_ plus eight characters). The full value appears once. Revoke a lost key and create a new one. Nothing is emailed.
API key security for law firms comes down to a few habits:
- One key per tool, named for that tool.
- A read-only API key for every AI or MCP client.
- The secret in a password manager or secrets manager.
- A look at Last used. "Never used" means the tool has not called, or it is calling with another secret.
- Revoke an API key when a vendor or a staff member who held the secret leaves.
Revoke asks "Revoke this API key? This will break any integrations using it." The button reads "Revoking..." while it runs. The key is deleted immediately. Later calls return 401, "Unauthorized - invalid or expired API key".
Creation, listing, revocation, and each use go to the audit trail. Last used updates when the key is used. API key security for law firms also means the owner or admin clicks Create API key and Revoke, and confirms each revoke. The practice management API is those /api/... calls.
Want team-scoped law firm API keys with Read only or Read and write, revocable any time? Sign up for LawyerLink and create the key under Slack & API. Name it for the tool, copy it once, and revoke it when the job ends.
Related posts
Law Firm Slack Integration: Case, Call, and SMS Alerts Without Oversharing
Set up a law firm Slack integration in MyLawyerLink: pick one channel, choose case, call, SMS, and invoice events, and keep sensitive details redacted.
Why an Audit Trail Matters for Modern Law Firms
A durable activity history helps firms answer โwho did what, when?โโfor security, operations, and peace of mindโwithout digging through email threads.
Secure Communication with Clients - A Modern Approach
Why secure communication matters for law firms and how MyLawyerLink helps you stay compliant.