Cityworks API
A REST API exists but is documented per customer instance at each deployment's /apidocs endpoint, with no central developer portal. Access effectively requires being a licensed Cityworks customer or partner. The v23 switch to a custom token header broke older integrations.
Frequently asked questions
Cityworks scores F on Supergood's API Report Card. A REST API exists but is documented per customer instance at each deployment's /apidocs endpoint, with no central developer portal. Access effectively requires being a licensed Cityworks customer or partner. The v23 switch to a custom token header broke older integrations.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Cityworks (now branded Trimble Cityworks under Trimble's Asset Lifecycle business) is a GIS-centric enterprise asset management (EAM) and work management platform for public infrastructure.
Government / Public Sector, specifically local governments (cities, counties), water/wastewater and electric utilities, transportation agencies, airports, and public works departments. Field crews and dispatchers use Cityworks to create and close work orders against geospatially located assets (pipes, hydrants, signals, pavement, signs, etc.), log inspections, track service requests from 311/citizen portals, schedule preventive maintenance, manage parts/inventory, and administer permits and licenses (PLL).
High within its niche. Cityworks reported over 700 utilities and local governments using the platform at the time of the Trimble acquisition, and it is regularly cited by Gartner Peer Insights and Capterra as a leading EAM solution for public sector infrastructure.
Cityworks holds the operational lifeblood of public works and utility agencies: every work order and labor/equipment cost, every service request from residents (often integrated with 311/SeeClickFix), inspection histories, preventive maintenance schedules, asset condition and risk scores, inventory/parts movement, capital project costs, and permitting and licensing records.
Mature and somewhat antiquated. The product traces back to 1996 and shows its age, reviewers consistently describe the UI as clunky, slow, and difficult to customize.
API and webhooks do not cover all integration scenarios, forcing custom solutions. API documentation is instance-hosted rather than centrally published, making discovery and onboarding hard for new integrators. Full sourced list under Sources below.
Common alternatives include Cartegraph (OpenGov), Lucity (CentralSquare), IBM Maximo, Brightly Asset Essentials (Siemens), VertiGIS / Esri ArcGIS Field Maps + workflows, Forerunner. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official Cityworks MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Cityworks doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.