OpenGov API
REST APIs exist for Permitting & Licensing and Procurement, plus a genuinely public CKAN open-data API. Keys are issued only inside a customer tenant; there is no self-serve signup, sandbox, or published rate limit. The ERP general ledger and Cartegraph have no public surface.
Frequently asked questions
OpenGov scores F on the API Report Card. REST APIs exist for Permitting & Licensing and Procurement, plus a genuinely public CKAN open-data API. Keys are issued only inside a customer tenant; there is no self-serve signup, sandbox, or published rate limit. The ERP general ledger and Cartegraph have no public surface.
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.
OpenGov is a Cox Enterprises-owned cloud software company building an integrated suite of applications for U.S. state and local government, headquartered in Redwood City, California.
Government / Public Sector, U.S. cities, counties, towns, special districts, and U.S. states, plus a small public-higher-ed and tribal-government footprint. Finance staff use OpenGov Financials and Budgeting & Planning to run the general ledger, accounts payable, purchasing, and the multi-year budget cycle, publishing transparency dashboards to constituents via OpenGov Stories/Open Data.
High within its segment, modest in absolute terms. OpenGov reports 2,000+ communities and 4,500+ successful software implementations.
OpenGov holds the operating data for thousands of U.S. local governments across the financial, permitting, procurement, and asset-management functions of municipal life: general ledger, accounts payable, payroll, multi-year budgets and budget books for 2,000+ cities and counties (Financials, Budgeting & Performance); every building permit, planning case, business license, code-enforcement record, inspection result, and applicant document on ViewPoint Cloud (Permitting & Licensing); every solicitation, vendor bid, evaluation score, and awarded contract on ProcureNow (Procurement); every asset inventory record, work order, inspection, and capital plan on Cartegraph (Asset Management); utility billing and tax revenue records (Tax & Revenue, Utility Billing); 311 service requests and constituent engagement responses (CRM, Peak Democracy); and the published open-data layer of dataset, resource, and view records on CKAN (Open Data).
Modern.
API documentation pages on developer.opengov.com require login/authentication to view, so developers cannot evaluate endpoints, schemas, or auth flows before becoming a customer. No published rate limits, SLAs, or status page for the Permitting & Licensing or Procurement APIs, limits are discovered through support tickets after customers hit them. Full sourced list under Sources below.
Common alternatives include Tyler Technologies, CentralSquare Technologies, Accela, BS&A Software, Euna Solutions (rollup of Bonfire, Questica, eSCRIBE), ClearGov. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.
Yes. Supergood maintains an unofficial OpenGov API and MCP server so AI agents and internal tools can read and write OpenGov data. See the OpenGov integration docs at supergood.ai/docs/opengov-api.