MyFileRunner API
MyFileRunner is a court e‑filing portal that enables attorneys and legal professionals to submit new case initiations and subsequent filings to participating courts, manage eService contacts, pay fees, and receive clerk decisions, stamped documents, and receipts. This page is an independent design exercise that asks what a well-designed MyFileRunner API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed MyFileRunner API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing MyFileRunner product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is MyFileRunner?
MyFileRunner is a court e‑filing portal that enables attorneys and legal professionals to submit new case initiations and subsequent filings to participating courts, manage eService contacts, pay fees, and receive clerk decisions, stamped documents, and receipts. It streamlines the end‑to‑end e‑filing process with guided filing codes, jurisdiction selections, and envelope tracking.
Core product areas include:
- E‑Filing Workflows (New case initiation, subsequent filings, envelope creation and submission)
- Case Search & Metadata (Cause numbers, parties, courts, case types)
- EService Management (Service contact rosters, proof of service notifications)
- Payments & Receipts (Fee calculation, payment accounts, downloadable receipts)
- Status Tracking & Decisions (Pending, accepted, rejected, clerk comments)
- Document Handling (PDF validation, file‑stamps, versioning)
- Firm & User Management (Firm accounts, attorneys, bar numbers, permissions)
An API for a platform like this would naturally organize around its core data entities:
- Firms & Users (Firm info, roles, attorney bar numbers)
- Cases (Court, county, cause number, case type, parties)
- Envelopes/Filings (Filing code, documents, fees, submission status, clerk comments)
- Documents (PDFs, versions, file‑stamped outputs)
- Service Contacts (Recipients for eService with email, role, party associations)
- Courts & Filing Locations (Jurisdiction, location codes)
- Fees & Payments (Breakdowns, totals, payment accounts, receipts)
- Notifications & Audit Events (Submission, acceptance, rejection, evidence)
The MyFileRunner Integration Challenge
Law firms rely on MyFileRunner daily, but turning portal‑centric e‑filing into API‑driven automation, especially inside iManage, can be challenging:
- Jurisdiction nuance: Court/location codes, case types, and filing codes vary by court and dictate fees and acceptance likelihood
- Long‑running workflows: Clerk review can take minutes to hours; submissions and resubmissions need asynchronous handling and reliable polling/webhooks
- Document compliance: PDF/A requirements, page size, redactions, and file‑stamp behavior must be validated prior to submission
- Service lists: Maintaining accurate eService rosters across matters and cases requires deduplication and party/role mapping
- Payment accounts: Fee estimates vs. actuals and receipt retrieval must be reconciled to the correct client/matter for cost recovery
- Authentication complexity: MFA and session lifecycles complicate headless automation across firm users
What a MyFileRunner API Could Look Like
If MyFileRunner exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The sections below flesh out this hypothetical design.
How AI agents could connect to software like MyFileRunner: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Use Cases
File From iManage Workspaces
- Push PDFs from iManage directly into a MyFileRunner envelope - Map iManage client/matter numbers to court/jurisdiction metadata - Capture accepted file‑stamped documents and store them back in the workspace with immutable audit data
Case Intake & Docket Synchronization
- Search and register cases by cause number, court, party names, or attorney - Maintain a consolidated docket view with envelope statuses and clerk decisions - Export case metadata for your matter management or CRM
Rejection Handling & Resubmission Automation
- Detect rejection reasons and clerk comments - Automatically regenerate compliant PDFs (e.g., metadata, page size) and resubmit with updated filing codes - Track resubmission threads and outcomes per matter
Cost Recovery & Receipts Sync
- Retrieve fee breakdowns and final receipts - Post receipts to iManage or your accounting system tagged with client/matter - Support audits with normalized payment records and evidence
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require username/password with MFA (SMS, email, TOTP); supports service accounts or customer‑managed credentials
Response format
JSON with consistent resource schemas and pagination across modules
Rate limits
Tuned for enterprise throughput while honoring firm entitlements and usage controls
Session management
Would need automatic reauth and cookie/session rotation with health checks
Data freshness
Near real‑time retrieval of case metadata, envelope statuses, file‑stamps, and receipts
Security
Encrypted transport, scoped tokens, and audit logging; respects MyFileRunner role‑based permissions
Webhooks
Optional asynchronous delivery for long‑running workflows (e.g., clerk acceptance events, rejection notices)
Latency
Design target: sub‑second responses for list/detail queries; acceptance/rejection times reflect court/clerk behavior
Throughput
Design target: designed for high‑volume filings, service roster synchronization, and receipt harvesting across matters
Reliability
Retry logic, backoff, and idempotency keys minimize duplicates and support at‑least‑once processing
Versioning
Clear versioning and change management would matter as MyFileRunner evolves
Frequently asked questions
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual MyFileRunner product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.