MyFileRunner API
MyFileRunner is an electronic filing service provider (EFSP) used by law firms to open new cases and submit subsequent filings to state courts, manage eService, pay filing fees, and track clerk acceptance or rejection. An unofficial API lets you pull case details, filing statuses, fil
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)
Common 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: SSO/MFA and session lifecycles complicate headless automation across firm users
How Supergood Creates MyFileRunner APIs
Supergood reverse‑engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your MyFileRunner tenant.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes case, envelope, service contact, and payment objects so you can integrate once and rely on consistent schemas
- Aligns with firm entitlements and role‑based permissions to ensure compliant access
- Supports high‑volume operations (bulk filings, roster sync) with polling or webhooks for long‑running jobs
- Bridges iManage with matter‑centric metadata mapping (client/matter ↔ cause number/court) and document version handling
Getting Started
- Schedule Integration Assessment
Book a 30‑minute session to confirm your jurisdictions, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened MyFileRunner adapter tailored to your firm workflows, iManage mapping, and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as MyFileRunner evolves.
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
Technical Specifications
Authentication
Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; 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
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
Sub‑second responses for list/detail queries under normal load; acceptance/rejection times reflect court/clerk behavior
Throughput
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
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Frequently asked questions
Yes. We can create envelopes for case initiations (with parties and case type) and subsequent filings against existing cause numbers, including fee estimation and payment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling and monitoring for session expiry.
Yes. We provide normalized links and signed downloads for file‑stamped documents and receipts, and can post them back to the correct iManage workspace with client/matter tagging.
We run pre‑flight checks (PDF/A, page size, metadata) and return actionable errors. When possible, we apply automated remediations or expose guidance to regenerate compliant PDFs.
Yes. We can create, update, and attach service contacts to cases, deduplicate recipients, and synchronize notification preferences across your matter system.