Cartegraph API
Cartegraph (now OpenGov Enterprise Asset Management) is a public-sector asset and operations management platform used by over 2,000 government agencies to track infrastructure assets, manage work orders, run inspections, and plan capital improvements. An unofficial API lets you programmatically pull assets, work orders, requests, inspections, and condition data—and push updates like new work orders, completed tasks, and status changes back into Cartegraph.
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
Common 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
How Supergood Creates Cartegraph APIs
Supergood reverse-engineers authenticated browser flows, the Cartegraph OMS REST API, and mobile-app surfaces to deliver a resilient API layer for your Cartegraph tenant—across asset, work, and request data.
- Handles username/password sign-in and session-cookie management securely
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across Assets, Work Orders, Requests, and Inspections so you integrate once and rely on consistent objects
- Aligns with each agency's configured asset classes, custom fields, and GIS layers to ensure accurate access
Use Cartegraph with AI agents: Cartegraph MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your asset classes, modules, and authentication model.
- Supergood Generates and Validates Your API
We deliver a hardened, production-ready Cartegraph adapter tailored to your agency configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Cartegraph and the OpenGov platform evolve.
API Endpoints
Authentication
/authenticateAuthenticate to a Cartegraph OMS tenant with username/password and obtain a session cookie for downstream calls.
Assets
/assetsList infrastructure assets across configured classes (transportation, water, parks, facilities, fleet) with class, status, and location filters.
Work Management
/work_ordersRetrieve work orders with tasks, labor, equipment, and material costs filtered by status, asset, and assignment.
Work Management
/create_work_orderCreate a new work order against one or more assets with tasks, scheduled dates, and crew assignments.
Requests
/requestsPull citizen and internal service requests with status, category, and linked-asset filters.
Inspections
/inspectionsRetrieve 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 Specifications
Authentication
Username/password sign-in with session-cookie management handled in a managed session
Connectivity
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
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
Sub-second reads on cached entities; multi-second writes when posting work orders and inspections
Throughput
Horizontally scaled workers sized to multi-department asset and work volume
Reliability
Retry, backoff, and idempotency keys for work order and inspection transactions
Adaptation
Continuous monitoring of Cartegraph releases, OpenGov platform changes, and agency-specific configuration drift
Frequently asked questions
Yes. Cartegraph is now OpenGov Enterprise Asset Management. Supergood works against the same authenticated surfaces and Cartegraph OMS REST API regardless of the product naming, and tracks endpoint changes as the platform migrates into OpenGov.
Each tenant is profiled against its configured asset classes, recordsets, layouts, and custom fields. Supergood preserves agency-specific fields and lifecycle states rather than forcing a generic schema.
Yes. Work orders, inspections, and asset updates captured in the field flow into the same records Supergood reads, so mobile-originated data is available through the normalized API surface.
Cartegraph assets are tightly coupled to Esri geometry. Supergood preserves the GIS context on each asset so spatial layers and locations remain available alongside operational records.
No. Supergood works with your existing Cartegraph credentials and authenticated sessions. No separate partner program or developer-portal approval is required to access your own agency's data.