Tyler Technologies API
Tyler Technologies is the largest public-sector software vendor in North America, providing ERP, courts and justice, public safety, appraisal and tax, permitting, schools, and payments software to state and local governments and K-12 districts. An unofficial API lets you programmatically pull permits and licenses, court cases and filings, CAD/RMS public safety records, parcels and tax bills, financial transactions, and student transportation data—and push updates like permit applications, case filings, payments, and work orders back into Tyler products such as Enterprise ERP, Munis, Odyssey, New World, and Enterprise Permitting & Licensing.
What is Tyler Technologies?
Tyler Technologies is the largest provider of integrated software and technology services to the public sector in North America. Tyler’s portfolio spans ERP and financials, courts and justice, public safety, appraisal and tax, civic services and permitting, K-12 student transportation and school ERP, payments, and data and insights—serving local and state governments, counties, municipalities, courts, special districts, and school districts.
Tyler is unusual among enterprise vendors because it is fragmented into many distinct product lines acquired and built over decades—Munis, Eden, MUNIS Self Service, New World ERP, Odyssey, Enterprise Justice, Enterprise Public Safety, New World Public Safety, Enterprise Permitting & Licensing, Enterprise Asset Management, Enterprise Assessment & Tax, School ERP Pro, Versatrans, and many more—each with its own data model, deployment patterns, and per-jurisdiction configuration.
Core product families include:
- ERP & Financials (Enterprise ERP, Munis, New World ERP, ERP Pro, AP Automation, Time & Attendance, Priority Based Budgeting)
- Courts & Justice (Odyssey/Enterprise Justice, Enterprise Jury Manager, CertiFile, Civil Process, Virtual Court, Court Analytics, Municipal Justice)
- Public Safety (Enterprise Public Safety, New World Public Safety, Enforcement Mobile, Public Safety Pro, Public Safety Analytics)
- Civic Services (Enterprise Permitting & Licensing, Permitting & Licensing Pro, Enterprise Service Requests, Enterprise Asset Management, Parks & Rec, Motor Vehicle & Driver Services)
- Appraisal & Tax (Enterprise Assessment & Tax, Assessment & Tax Plus/Pro, CA Valuation, Tax-Wise, SmartFile, Enterprise Records Management)
- Schools (School ERP Pro, SISFin, Student Transportation, Versatrans, Tyler Drive, Telematic GPS, Absence & Substitute, Onboard iPaaS)
- Corrections (Enterprise Corrections, Enterprise Supervision)
- Payments, Data & Insights, Cybersecurity, and the Tyler Platform Alliance partner ecosystem
Common data entities:
- Permits, Licenses, Inspections, Code Cases, Service Requests
- Court Cases, Filings, Hearings, Dockets, Jurors, Warrants, Civil Process Items
- CAD Incidents, RMS Reports, Arrests, Citations, Field Interviews, Evidence
- Parcels, Property Records, Valuations, Tax Bills, Payments, Exemptions
- ERP: Vendors, Purchase Orders, Invoices, GL Accounts, Funds, Budgets, Employees, Payroll
- Schools: Students, Routes, Stops, Vehicles, Drivers, Substitute Assignments, Attendance
- Users, Roles, Departments/Agencies, Jurisdictions, Audit Trails, Attachments
The Tyler Technologies Integration Challenge
Counties, cities, courts, and school districts run their day-to-day operations on Tyler—but turning portal- and report-driven workflows into API-driven automation is genuinely hard:
- Product-line breadth: Munis, Eden, Odyssey, New World, Enterprise ERP, Enterprise Permitting & Licensing, and Versatrans each have different data models, schemas, and access patterns—there is no single “Tyler API”
- Per-jurisdiction implementations: Counties, courts, and districts heavily customize fields, code tables, workflows, and security; the same product behaves differently from one jurisdiction to the next
- Mixed deployment landscape: A blend of Tyler-hosted SaaS, on-premise, and hybrid installs means endpoints, hostnames, and authentication models vary by customer
- Authentication complexity: SSO via SAML/OAuth (often through state or county IdPs), MFA, and role-bound session cookies make headless automation non-trivial
- Partnership-gated APIs: Where APIs exist, access typically runs through the Tyler Platform Alliance partner program rather than a self-serve developer portal
- Report-driven exports: Critical data often lives behind canned reports, scheduled extracts, or on-prem databases—schemas and performance vary widely by jurisdiction
- Public-record handling: Court filings, permits, and tax records carry redaction, sealing, and retention rules that any integration must respect
How Supergood Creates Tyler Technologies APIs
Supergood reverse-engineers authenticated browser flows, internal web services, and report endpoints across Tyler’s product lines to deliver a resilient API layer matched to your specific Tyler products and jurisdiction.
Whether your environment is Munis, Odyssey, New World, Enterprise Permitting & Licensing, or a combination of several, Supergood adapts to the products and configuration you actually run.
- Handles username/password, SSO/OAuth (including state and county IdPs), and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection across Tyler-hosted, on-premise, and hybrid deployments
- Normalizes responses across product lines and jurisdictions so you integrate once and rely on consistent objects across permits, cases, parcels, and ERP records
- Aligns with role-based permissions, public-record rules, and jurisdiction-specific configuration to ensure compliant access
Use Tyler Technologies with AI agents: Tyler Technologies MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm which Tyler products you run, your jurisdiction, and your authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Tyler adapter tailored to your product mix, jurisdictional configuration, and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Tyler products and jurisdiction-specific configurations evolve.
API Endpoints
Authentication
/authenticateAuthenticate to a Tyler product (Munis, Odyssey, EnerGov, etc.) including SSO and MFA
Permits
/permitsRetrieve permit records from Enterprise Permitting & Licensing (EnerGov)
Permits
/submit_applicationSubmit a permit, license, or service-request application into Tyler
Licensing
/licensesRetrieve business and professional licenses managed in Tyler
Inspections
/inspectionsRetrieve inspection schedules, results, and code-case status
Records
/create_recordCreate a record (case filing, work order, citation) in the appropriate Tyler product
Use Cases
Sync ERP and Permitting Data Across Munis and EnerGov
- Reconcile vendor, GL, and project records between Enterprise ERP/Munis and Enterprise Permitting & Licensing (EnerGov) - Push permit fees and inspection charges into accounts receivable without dual entry - Keep funds, departments, and code tables in sync across both systems
Automate Court Case Data from Odyssey
- Stream Odyssey filings, hearings, dockets, and dispositions into downstream analytics and case-management tools - Trigger downstream workflows on new charges, warrants, or jury events - Power public-records portals and attorney workflows with current case data
Public Safety Dispatch and RMS Sync
- Pull CAD incidents, RMS reports, citations, and arrests from Enterprise/New World Public Safety - Feed real-time incident data into BI tools, transparency dashboards, and federal reporting (NIBRS) - Coordinate dispatch context across neighboring agencies and partner platforms
School District SIS and Transportation Integration
- Sync students, routes, stops, and attendance between Tyler SIS, Versatrans, and third-party tools - Automate substitute and absence workflows alongside HR and payroll in School ERP Pro - Keep parent-facing apps current with bus, route, and schedule changes
Technical Specifications
Authentication
Username/password, SSO via SAML/OAuth (often through state or county IdPs), and MFA (SMS, email, TOTP) handled per Tyler product and jurisdiction
Connectivity
REST and SOAP endpoints across Munis, Eden, Odyssey, New World, and EnerGov; access typically gated through the Tyler Platform Alliance partner program
Response format
JSON and XML responses normalized into consistent objects across product lines and per-jurisdiction configurations
Rate limits
Vary by Tyler product, hosting model, and partner agreement; Supergood applies adaptive throttling and backoff per environment
Session management
Automated cookie and token refresh across Tyler-hosted SaaS, on-premise, and hybrid deployments, including IdP-mediated SSO sessions
Data freshness
Near real-time reads for portal-backed entities; report- and extract-driven data refreshed on configurable schedules per jurisdiction
Security
TLS in transit, encrypted credential storage, role-based scoping aligned with Tyler product permissions and public-record rules (redaction, sealing, retention)
Webhooks
Change-detection layer emits events on new permits, court filings, CAD incidents, and ERP transactions when native push isn't available
Latency
Sub-second for most authenticated reads; longer for report-driven exports and large jurisdictional datasets
Throughput
Scales with Tyler tenant and product entitlements; Supergood batches and parallelizes reads to maximize sustainable throughput
Reliability
Continuous monitoring across product lines and jurisdictions, with automatic recovery from auth, schema, and configuration changes
Adaptation
Supergood automatically adjusts to Tyler product updates, per-jurisdiction customization, and shifts in deployment model (Tyler-hosted, on-prem, hybrid)
Frequently asked questions
Supergood adapts to the specific Tyler products you run, including Enterprise ERP/Munis, Eden, New World ERP, Odyssey/Enterprise Justice, Enterprise and New World Public Safety, Enterprise Permitting & Licensing (EnerGov), Enterprise Assessment & Tax, School ERP Pro, and Versatrans. Coverage is scoped during the integration assessment based on your environment.
Yes. Many counties and cities run multiple Tyler products together. Supergood treats Munis/Enterprise ERP, Odyssey, and Enterprise/New World Public Safety as separate adapters that share authentication, jurisdiction context, and audit conventions, so you get a coherent integration across financials, courts, and dispatch/RMS data.
Yes. Supergood handles all three. We adapt to the endpoints, hostnames, and authentication models specific to your hosting environment, including state or county SSO providers in front of Tyler's products.
Where Tyler exposes official APIs, access often runs through the Tyler Platform Alliance partner program rather than a self-serve developer portal. Supergood works with customers and partners alongside that program; for products without partner-API coverage, we reverse-engineer authenticated portal and report flows to provide the same capability.
Counties, cities, courts, and school districts customize fields, code tables, workflows, and permissions in Tyler. Supergood maps your jurisdiction's specific configuration during onboarding and continuously adapts as code tables, security roles, and product versions evolve, so the API stays aligned with how your jurisdiction actually runs Tyler.