Submit a court filing via the Tyler EFM OASIS ECF 4.01 SOAP interface and capture the FilingReviewCommitteeMessageID returned in the submission acknowledgment response
Poll the GetFilingList or GetFiling SOAP operation at intervals compliant with the court's acceptable polling frequency, supplying the previously captured message ID to retrieve the current review status
Parse the returned FilingStatusCode from the response (e.g., Submitted, Accepted, Rejected) and extract any court-provided rejection reason text from the ReviewComment or RejectReason elements
If the status is Accepted, retrieve the court-assigned case number and document-stamp data from the response and update the matter management system with the official filing metadata
If the status is Rejected, parse the rejection code against the ECF standard rejection code enumeration to determine whether the deficiency is correctable (e.g., missing attachment) and trigger a corrected re-filing workflow
Known gotchas
Tyler Odyssey EFM instances are court-specific; WSDL endpoint URLs, authentication credentials, and supported rejection code sets vary by jurisdiction and even by court within the same state — never assume one court's configuration generalizes to another
Some courts impose minimum polling intervals and will return errors or blacklist clients that poll too frequently; implement exponential backoff starting at the court's documented minimum interval
The FilingReviewCommitteeMessageID is a correlation key for the EFM session, not a permanent court record identifier; accepted filings receive a separate EnvelopeID or court case number that is the authoritative long-term reference
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