Integrate an e-filing service provider application with a state court's Tyler Technologies Electronic Filing Manager (EFM).
domain: tylertech.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Confirm the target court's e-filing standard version (most Tyler EFM courts implement an OASIS ECF-based interface) and obtain that court's specific EFM endpoint/WSDL and onboarding requirements.
Register your application as an approved electronic filing service provider (EFSP) with the court or Tyler and obtain firm/user credentials for a UAT (test) environment before production access.
Implement the core filing lifecycle calls: retrieve case/court metadata, calculate filing fees, submit a filing envelope (documents plus case data), and poll for review status.
Handle asynchronous review callbacks or polling, since court clerks accept, reject, or return filings for correction rather than confirming instantly.
Test each case type and document type against the court's UAT/staging EFM instance before moving to production filings.
Expect court- and state-specific configuration differences (fee schedules, permitted case types) since each Tyler EFM deployment is independently configured per jurisdiction.
Known gotchas
There is no single universal public Tyler EFM API — every court/state configures its own EFM instance, endpoints, and case types, so integration details must come from that specific court or Tyler, not be assumed from another jurisdiction.
Filing acceptance is asynchronous: envelopes go through clerk review and can be rejected or returned for correction, so integrations must poll/handle status changes rather than treat submission as final.
Many deployments still use SOAP/WS-Security per the OASIS ECF standard; verify whether your target court has moved to a newer version before coding against outdated samples.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?