













































PubWorks is public works management software for cities, counties, and road and highway departments, providing work order tracking, asset management, job costing, fleet maintenance, and service request tracking. It is used by public works crews and managers to record labor, equipment, and material costs against assets.
Have any questions? We’re here to help You
Some editions of PubWorks expose an API, but it is often limited, legacy, or inconsistent between versions, and many on-prem deployments have no usable API at all. Makini gives you one modern REST API for PubWorks that lets you read and write PubWorks data, even for legacy or on-prem instances. You build against Makini once instead of integrating with PubWorks directly.
You integrate PubWorks through Makini's Unified API. Authenticate once and Makini normalizes PubWorks data into a single consistent schema you can read from and write to inside your product. The same connection reaches PubWorks plus 2,000+ other ERP, WMS and CMMS systems, so you build one integration instead of one per system.
Through Makini you can read and write PubWorks's core records as normalized, standardized resources, in both directions: pull data out of PubWorks and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across PubWorks and every other connected system.
Days, not quarters. Because Makini already builds and maintains the PubWorks connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing PubWorks data through the Unified API, typically within a few days. A PubWorks integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to PubWorks over encrypted connections on SOC 2 Type II certified infrastructure, and handles PubWorks credentials for you so they are never exposed to your app. You authenticate once, and access runs through Makini's managed, auditable layer. The same security model applies across PubWorks and every other connected system.
Makini owns the maintenance. When PubWorks changes its API, versions, or endpoints, Makini updates the connector, and your integration keeps working with no changes on your side. You get a stable Unified API with webhooks, and PubWorks upkeep stays off your roadmap.
