Cartegraph API
Cartegraph, now OpenGov Enterprise Asset Management, is a cloud asset and operations management platform built for the public sector. This page is an independent design exercise that asks what a well-designed Cartegraph API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed Cartegraph API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing Cartegraph product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is Cartegraph?
Cartegraph, now OpenGov Enterprise Asset Management, is a cloud asset and operations management platform built for the public sector. Trusted by more than 2,000 public agencies including towns, cities, and counties, it helps governments manage infrastructure assets, simplify work orders, run inspections, plan capital improvement projects, and optimize crews and resources across transportation, water, wastewater, parks, facilities, and fleet operations.
Core product areas include:
- Asset Management & Tracking (GIS integration, condition tracking, cost monitoring, work history, live dashboards)
- Work Management (mobile field app, work orders, task assignment, crew coordination)
- Planning & Analytics (Scenario Builder for capital improvement forecasting, risk evaluation, funding scenarios)
- OG Assist AI (natural-language queries on asset records, inspection history, and maintenance needs)
- Esri GIS integration plus connectors to Permitting & Licensing, 311, and 811 systems
An API for a platform like this would naturally organize around its core data entities:
- Assets (infrastructure items across transportation, water, parks, facilities, fleet)
- Work Orders, Tasks, Labor, Equipment, and Material costs
- Requests (citizen and internal service requests)
- Inspections and Condition Assessments
- Capital Improvement Scenarios, Risk and Funding plans
The Cartegraph Integration Challenge
Agencies run mission-critical operations on Cartegraph daily, but turning portal- and mobile-driven workflows into API-driven automation is non-trivial:
- Agency-by-agency configuration: Asset classes, layouts, fields, and workflows are tailored per government, generic integrations break across tenants
- Cookie-based session auth: The Cartegraph OMS REST API authenticates and returns a session cookie that must be maintained across calls, complicating headless automation
- Mobile-captured field data: Work orders, inspections, and asset updates flow through the mobile app, so much operational data never touches a clean export
- GIS coupling: Assets are tightly bound to Esri geometry and spatial layers, so records can't be reasoned about without their geospatial context
- Class and field variability: Endpoint coverage depends on which asset classes, custom fields, and recordsets each agency has configured
- Platform migration: As Cartegraph folds into the OpenGov Public Service Platform, endpoints, auth, and product naming continue to shift
What a Cartegraph API Could Look Like
If Cartegraph exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like Cartegraph: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate to a Cartegraph OMS tenant with username/password and obtain a session cookie for downstream calls.
Assets
/assetsWould list infrastructure assets across configured classes (transportation, water, parks, facilities, fleet) with class, status, and location filters.
Work Management
/work_ordersWould retrieve work orders with tasks, labor, equipment, and material costs filtered by status, asset, and assignment.
Work Management
/create_work_orderWould create a new work order against one or more assets with tasks, scheduled dates, and crew assignments.
Requests
/requestsWould pull citizen and internal service requests with status, category, and linked-asset filters.
Inspections
/inspectionsWould retrieve inspections and condition assessments with asset, date, and result filters.
Use Cases
Sync asset and work data into a central warehouse
- Pull assets, classes, and condition scores across transportation, water, parks, and facilities - Stream work orders, tasks, and labor/equipment costs to downstream BI and reporting - Reconcile asset hierarchies and GIS geometry for a unified infrastructure 360
Automate work order creation and updates
- Push new work orders and tasks from 311, IoT, or maintenance triggers without portal clicks - Update task status, labor, and material usage from field and third-party systems - Route completed work and inspection results back to crews and supervisors
Close the loop on citizen requests
- Pull service requests and link them to the affected assets - Trigger work orders automatically when a request meets agency thresholds - Sync request and resolution status back to 311 and constituent portals
Power capital planning and inspections
- Export condition assessments and inspection histories for capital improvement scenarios - Feed risk and funding models in Scenario Builder with current asset data - Surface assets due for inspection or replacement to planning workflows
Technical Requirements
Authentication
Would require username/password sign-in with session-cookie management with managed session handling
Connectivity
Would build on authenticated browser flows plus the Cartegraph OMS REST API and mobile-app surfaces where exposed by the agency
Response format
Normalized JSON across Assets, Work Orders, Requests, and Inspections objects
Rate limits
Adaptive throttling tuned to your tenant to avoid agency-side limits
Session management
Would need automatic session-cookie refresh, re-auth handling, and credential rotation
Data freshness
Near real-time pulls for assets, work orders, and requests with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for work order creation, status changes, inspection completion, and new requests
Latency
Design target: sub-second reads on cached entities; multi-second writes when posting work orders and inspections
Throughput
Design target: horizontally scaled workers sized to multi-department asset and work volume
Reliability
Retry, backoff, and idempotency keys for work order and inspection transactions
Versioning
Clear versioning and change management would matter as Cartegraph evolves
Frequently asked questions
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual Cartegraph product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.