MyFileRunner

Supergood | MyFileRunner API

Alex Klarfeld

Alex Klarfeld

— 7 min read
Supergood | MyFileRunner API

Programmatically access court e‑filing, case lookup, envelopes, eService contacts, clerk decisions, file‑stamped documents, and receipts from MyFileRunner with a stable REST API. Supergood builds and operates production‑grade, unofficial MyFileRunner integrations so your team can automate litigation workflows without heavy custom engineering.

Plain English: 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, file‑stamped PDFs, and receipts—and push new filings, service lists, and corrections when clerks request changes.

For a tech company integrating with MyFileRunner—especially if your customers live in iManage—this means you can file directly from a client/matter workspace, attach documents without manual downloads, sync accepted file‑stamps and receipts back to the DMS, maintain a unified docket view, and automate resubmissions when filings are rejected. You can build features like “File from iManage,” automated service roster management, matter‑centric envelope tracking, and cost‑recovery workflows that reconcile fees and receipts to the correct matter.

What is MyFileRunner?

MyFileRunner (https://www.myfilerunner.com) 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

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

Available Endpoints

Authentication

POST /sessions: Establish a session using firm credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short‑lived auth token maintained by the platform.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/sessions \
  --header 'Authorization: Basic <Base64 encoded token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "username": "[email protected]",
    "password": "<password>",
    "mfa": { "type": "totp", "code": "123456" }
  }'

Example response

{
  "authToken": "eyJhbGciOi...",
  "expiresIn": 3600,
  "user": {
    "id": "u_mfr_0b12a9",
    "name": "Paralegal User",
    "entitlements": ["cases", "filings", "serviceContacts", "payments"]
  }
}

POST /sessions/refresh: Refresh an existing token to keep sessions uninterrupted.

Cases

GET /cases: Search cases by court, cause number, party, or attorney bar number. Useful for mapping iManage matters to existing court records.

Query parameters

  • courtCode: string (jurisdiction/location code)
  • causeNumber: string
  • partyName: string
  • attorneyBarNumber: string
  • page, pageSize: integers for pagination

Example response

{
  "items": [
    {
      "caseId": "case_tx_dal_23-012345",
      "court": {"code": "TX-DAL-134", "name": "Dallas County District Court"},
      "causeNumber": "DC-23-012345",
      "caseType": "Contract",
      "status": "Open",
      "parties": [
        {"role": "Plaintiff", "name": "Acme Corp"},
        {"role": "Defendant", "name": "John Smith"}
      ],
      "createdAt": "2025-10-03T14:12:09Z"
    }
  ],
  "page": 1,
  "pageSize": 25,
  "total": 1
}

Filings

POST /filings: Create and submit an envelope for a new case or subsequent filing. Attach documents from iManage or provide direct uploads.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/filings \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "submissionType": "subsequent",
    "caseId": "case_tx_dal_23-012345",
    "court": {"code": "TX-DAL-134"},
    "filingCode": "Motion",
    "description": "Plaintiff\'s Motion to Compel",
    "documents": [
      {
        "source": "imanage",
        "docId": "NRTDB:47291.7",
        "version": 7,
        "fileName": "Motion_to_Compel.pdf",
        "isLead": true
      },
      {
        "source": "upload",
        "uploadToken": "upl_9b21f3",
        "fileName": "Exhibit_A.pdf",
        "isLead": false
      }
    ],
    "service": {
      "method": "electronic",
      "contacts": [
        {"contactId": "svc_1a2b3c", "partyRole": "Defendant"}
      ]
    },
    "fees": {"paymentAccountId": "pay_acc_98d1", "estimate": true},
    "metadata": {"imanage": {"clientId": "ACME", "matterId": "2023-014"}},
    "submit": true
  }'

Example response

{
  "envelopeId": "env_7c910e",
  "filingId": "fil_a032f9",
  "status": "submitted",
  "feeEstimate": {
    "total": 112.50,
    "breakdown": [
      {"code": "BASE", "amount": 75.00},
      {"code": "TECH", "amount": 27.50},
      {"code": "SERVICE", "amount": 10.00}
    ]
  },
  "service": {"method": "electronic", "contactsCount": 1},
  "createdAt": "2026-02-20T16:41:31Z"
}

GET /filings: List filings with filters for status, court, case, and update windows. Returns clerk decisions and file‑stamp links when available.

Query parameters

  • status: pending | accepted | rejected | withdrawn
  • caseId: string
  • courtCode: string
  • updatedFrom, updatedTo: ISO 8601 timestamps
  • page, pageSize: integers for pagination

Example response

{
  "items": [
    {
      "filingId": "fil_a032f9",
      "envelopeId": "env_7c910e",
      "caseId": "case_tx_dal_23-012345",
      "court": {"code": "TX-DAL-134", "name": "Dallas County District Court"},
      "filingCode": "Motion",
      "description": "Plaintiff\'s Motion to Compel",
      "status": "accepted",
      "clerkComments": null,
      "fileStampUrl": "https://files.supergood.ai/mfr/fil_a032f9/stamped.pdf",
      "receiptUrl": "https://files.supergood.ai/mfr/fil_a032f9/receipt.pdf",
      "fees": {"total": 108.75},
      "updatedAt": "2026-02-21T09:18:04Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Service Contacts

POST /service-contacts: Create or update an eService contact and optionally attach to a case. Useful for keeping service rosters aligned with your matter records.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/service-contacts \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Jane Attorney",
    "email": "[email protected]",
    "party": {"role": "Defendant", "name": "John Smith"},
    "caseId": "case_tx_dal_23-012345",
    "tags": ["defense", "primary"],
    "notifyOn": ["submission", "acceptance", "rejection"]
  }'

Example response

{
  "contactId": "svc_5f2e91",
  "caseId": "case_tx_dal_23-012345",
  "email": "[email protected]",
  "createdAt": "2026-02-20T16:45:10Z"
}

Get full API Specs →

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)

Performance Characteristics

  • 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

Getting Started

  1. Schedule Integration Assessment

Book a 30‑minute session to confirm your jurisdictions, licensing, and authentication model.

  1. Supergood Builds and Validates Your API

We deliver a hardened MyFileRunner adapter tailored to your firm workflows, iManage mapping, and entitlements.

  1. Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as MyFileRunner evolves.

Schedule Integration Call →

Frequently Asked Questions

Q: Do you support both new case and subsequent filings?

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.

Q: How are MFA and SSO handled for automation?

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.

Q: Can you pull file‑stamped PDFs and receipts back into iManage?

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.

Q: How do you validate documents before submission?

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.

Q: Can you manage eService rosters across cases?

Yes. We can create, update, and attach service contacts to cases, deduplicate recipients, and synchronize notification preferences across your matter system.

iManage Work API - File directly from your DMS and sync stamped PDFs & receipts

Ready to automate your MyFileRunner workflows?

Supergood can have your MyFileRunner integration live in days with no ongoing engineering maintenance.

Get Started →

Read more