Adapter-first modernization without a CMS rip-and-replace.
Court technology teams can connect portal workflows to existing Tyler, Journal, iDocket, payment, document, and notification systems.
Integration map
Public portal
Traffic, e-filing, eService, status, receipts.
Court CMS adapter
Create docket entries, post dispositions, attach documents.
EFM / EFSP adapter
Envelope submission, review callback, service contacts.
Payment adapter
Tokenization, authorization, capture, refund, settlement.
Citation / DMV adapter
Citation lookup, eligibility, proof requirements, points.
Notification adapter
Email, SMS, deficiency, receipt, service confirmation.
Adapter health
Court CMS adapter
Success 99.2% · 412ms
EFM / EFSP adapter
Success 98.7% · 380ms
Payment processor
Success 99.8% · 220ms
Document services
Success 97.4% · 590ms
Citation / DMV lookup
Success 94.6% · 1120ms
Notification service
Success 99.1% · 180ms
ECF-shaped payload preview
Local court payloads are normalized around OASIS LegalXML ECF and NIEM-compatible case, party, document, and service concepts.
{
"standard": "OASIS LegalXML ECF 5.01-inspired",
"message": "ReviewFilingCallbackMessage",
"filingId": "EFIL-2026-000381",
"case": {
"courtId": "court-bluebonnet-civil",
"caseType": "civil_contract",
"caseNumber": "CV-2026-1182"
},
"documents": [
{
"documentType": "motion",
"fileName": "motion-summary-judgment.pdf",
"confidential": false
}
],
"service": {
"contacts": 2,
"certificateStatus": "generated"
},
"reviewDecision": "accepted"
}Why this matters
Court technologists need clear seams for filing envelopes, review callbacks, CMS docketing, document storage, payment settlement, and notifications.