Register as an Electronic Filing Service Provider (EFSP) or use an existing EFSP account at efiletexas.gov; obtain EFSP credentials from Tyler Technologies
Construct a SOAP envelope conforming to OASIS LegalXML ECF 4.01 schema, populating FilingMessage with court, case, and party data in the required XML structure
Attach document payloads as base64-encoded MTOM/XOP attachments within the SOAP message; ensure PDFs meet court-specified size and format rules
POST the SOAP envelope to the Tyler EFM endpoint for the target court (court-specific WSDL URLs are distributed to registered EFSPs; do not hard-code a generic URL)
Parse the synchronous acknowledgement for a FilingReviewMessage; use the returned FilingID to poll filing status until the court reviewer accepts or returns the filing
On acceptance, retrieve the stamped/conformed copies from the FilingReviewMessage response or a subsequent status call and store them with the original FilingID
Known gotchas
Each Texas court has its own EFM endpoint URL and may enforce different local rules (page limits, PDF/A compliance, required envelope fields); verify with the specific court's EFSP guide before submitting
OASIS ECF 4.01 uses SOAP/MTOM — REST is not available; off-the-shelf REST clients will not work and you must use a SOAP library that supports MTOM attachments
Filing fees are calculated and collected at submission time through the EFSP; a missing or invalid payment method causes immediate rejection before the court even reviews the filing
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp