Submit an electronically filed civil complaint to a Texas district court through the Tyler Technologies Odyssey EFM using the OASIS ECF 4.01 SOAP interface
Register as an Electronic Filing Service Provider (EFSP) or use an existing EFSP with access to the Tyler EFM SOAP endpoint; direct filer access requires registration through the Tyler integration program
Construct a valid OASIS ECF 4.01 XML message body including the case type, relief type, filing party information, and attached document payloads encoded as base64 within the SOAP envelope
POST the SOAP message to the Tyler EFM endpoint for the target Texas court with the appropriate Content-Type: text/xml and SOAPAction headers
Parse the synchronous SOAP response for a filing status code; an accepted status returns a filing ID that can be polled for court review outcomes
Poll the filing status endpoint with the filing ID until the court accepts or rejects the submission; rejections include a reason code requiring a corrected re-submission
Known gotchas
The Tyler EFM uses OASIS ECF 4.01 SOAP, not REST; JSON payloads are not accepted and WSDL schema validation is strict — XML structure errors cause immediate rejection
Each Texas court may have court-specific filing codes, fee schedules, and accepted document formats that differ from the base OASIS ECF schema; always retrieve current court-specific configuration before filing
Lead documents must typically be PDF/A format and below a file size limit that varies by court; attachments exceeding limits will cause the entire submission to be rejected
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