# OpenGov > OpenGov builds cloud ERP and public service software for state and local government, serving more than 2,000 communities. The OpenGov Public Service Platform publishes a developer portal at developer.opengov.com with ten OpenAPI 3.x definitions covering roughly 358 operations across Permitting & Licensing, Budgeting & Performance, Procurement & Contract Management, Purchase Orders, Receipts, Vendor Management, Enterprise Asset Management and Open Data (CKAN). Access requires an OpenGov customer account — the specs and docs are fully public, the credentials are not. Generated by API Evangelist on 2026-08-04. OpenGov publishes its own llms.txt at https://developer.opengov.com/llms.txt (a link index of the portal's markdown docs); this file is the catalog-side companion covering the API surface and the artifacts derived from it. ## APIs - [Permitting & Licensing API v2](https://developer.opengov.com/catalog/plc-api): 113 operations. JSON:API shaped. Records, record types, approval/document/inspection/payment workflow steps, inspections and checklists, locations, projects, ledger entries, transactions, files, attachments with versioning, change requests, collections, guests, users, activity logs. Base: https://api.plce.opengov.com/plce - [Permitting & Licensing API v1](https://developer.opengov.com/catalog/plc-api): 10 operations. Superseded by v2. - [Budgeting & Performance API](https://developer.opengov.com/catalog/bnp-api): 10 operations. Budgets, budget amounts, chart of accounts, CSV data exports. Base: https://api.bnp.opengov.com - [Procurement & Contract Management API v2](https://developer.opengov.com/catalog/pro-api): 22 operations. Contracts, categories, tags, procurement datasets. Base: https://api.procurement.opengov.com - [Procurement & Contract Management API v1](https://developer.opengov.com/catalog/pro-api): 22 operations. Superseded by v2. - [Purchase Order API](https://developer.opengov.com/catalog/pro-purchase-order-api): 82 operations. Purchase order state machine (draft/submit/approve/issue/close), line items, change orders, terms, attachments, revisions, GL suggestions, spend summaries, invoice and receipt sync. Base: https://api-purchase-order.procurement.opengov.com - [Receipt API](https://developer.opengov.com/catalog/pro-receipt-api): 26 operations. Goods and services receipts against purchase orders. Base: https://api-receipts.procurement.opengov.com - [Vendor Management API](https://developer.opengov.com/catalog/vm-api): 44 operations. Vendor lifecycle, search and export, taskmaster approvals, contacts, certificates, attachments, notes, saved views, bulk CSV import. Base: https://api.vendor.opengov.com - [Enterprise Asset Management API](https://developer.opengov.com/catalog/eam-api): 13 operations. Generic business-object CRUD over classes (assets, work orders, requests, resources), class metadata, layouts, scenario commands. Cookie-session auth. Per-tenant server URL — OpenGov publishes no default host. - [Open Data CKAN Action API](https://developer.opengov.com/catalog/opendata-public-api): 16 operations. CKAN 2.9 package/resource/organization/group/tag actions. Per-customer Open Data portal hostname. ## Specs - [Permitting & Licensing v2 OpenAPI](https://developer.opengov.com/catalog/plc-api/v2/schema.yaml) - [Permitting & Licensing v1 OpenAPI](https://developer.opengov.com/catalog/plc-api/v1/schema.yaml) - [Budgeting & Performance OpenAPI](https://developer.opengov.com/catalog/bnp-api/1.0.0/schema.yaml) - [Procurement v2 OpenAPI](https://developer.opengov.com/catalog/pro-api/v2/schema.yaml) - [Procurement v1 OpenAPI](https://developer.opengov.com/catalog/pro-api/v1/schema.yaml) - [Purchase Order OpenAPI](https://developer.opengov.com/catalog/pro-purchase-order-api/1.0.0/schema.yaml) - [Receipt OpenAPI](https://developer.opengov.com/catalog/pro-receipt-api/1.0.0/schema.yaml) - [Vendor Management OpenAPI](https://developer.opengov.com/catalog/vm-api/1.0.0/schema.yaml) - [Enterprise Asset Management OpenAPI](https://developer.opengov.com/catalog/eam-api/1.0.0/schema.yaml) - [Open Data CKAN OpenAPI](https://developer.opengov.com/catalog/opendata-public-api/2.9/schema.yaml) ## Docs - [Developer Portal](https://developer.opengov.com) - [Overview](https://developer.opengov.com/docs/overview) - [Quickstart](https://developer.opengov.com/docs/quickstart) - [API Catalog](https://developer.opengov.com/catalog) - [Granting developer access](https://developer.opengov.com/docs/granting-developer-access) - [Creating integrations](https://developer.opengov.com/docs/app-management/app-creation) - [API keys](https://developer.opengov.com/docs/app-management/api-key) - [Permissions reference](https://developer.opengov.com/docs/app-management/permissions) - [Using the API Test Console](https://developer.opengov.com/docs/using-test-console) - [Permitting & Licensing access control](https://developer.opengov.com/docs/plc/access-control) - [Permitting & Licensing common use cases](https://developer.opengov.com/docs/plc/use-cases) - [SCIM 2.0 integration](https://developer.opengov.com/docs/access-control/overview) - [Webhooks overview](https://developer.opengov.com/docs/webhooks/overview) - [Webhook subscriptions and signature verification](https://developer.opengov.com/docs/webhooks/managing-subscriptions) - [Webhook event payloads](https://developer.opengov.com/docs/webhooks/event-payloads) - [Permitting & Licensing changelog](https://developer.opengov.com/docs/plc/changelog) - [Developer terms of use](https://developer.opengov.com/terms-of-use) - [OpenGov llms.txt](https://developer.opengov.com/llms.txt) ## Authentication - Integration API key in an `Authorization: Token ` header, issued per integration in the Developer Portal (Permitting & Licensing). - `X-API-KEY` or `Authorization` key generated in the product Control Panel (Budgeting & Performance, Procurement family). - Bearer JWT (Vendor Management, Purchase Order, Receipt). - OAuth 2.0 client_credentials via Auth0 at https://accounts.viewpointcloud.com/ (Permitting & Licensing openIdConnect scheme). Discovery: https://accounts.viewpointcloud.com/.well-known/openid-configuration - Session cookie via `POST /api/v1/authenticate` (Enterprise Asset Management only). - `Authorization: Bearer ` for SCIM 2.0. OAuth and Basic Auth are not supported for SCIM. Authorization is by named permission grants per integration (Record Read, Record Write, Workflow Write, …) plus per-Record-Type access. An administrator can only grant permissions they personally hold. ## Events - 31 Permitting & Licensing webhook events, HMAC-SHA256 signed with a per-subscription secret over `"."`, `X-Webhook-Signature: sha256=`, 5-minute replay tolerance, OPTIONS origin handshake against https://webhooks.opengov.com - No events for Enterprise Asset Management, Procurement or Vendor Management ("No events available yet") - No AsyncAPI document is published ## Operations, security and status - [Status page](https://status.opengov.com/) (Atlassian Statuspage, 10 components, 90-day uptime) - [Trust center](https://trust.opengov.com/) — SOC 2 Type 2, SOC 3, TX-RAMP, AZ RAMP, GovRAMP, GDPR, CCPA, CPRA, VPAT - [Security and responsible disclosure](https://opengov.com/security/) — security@opengov.com, safe harbor, 3-business-day acknowledgement - [Support / Help Center](https://support.opengov.com) - [Ideas portal](https://ideas.opengov.com) ## What OpenGov does not publish - No client SDK in any language, and no CLI - No sandbox, test mode or test credentials — the API Test Console runs against live production data - No `/.well-known/security.txt`, no `/.well-known/api-catalog`, no A2A agent card - No first-party MCP server (the npm `opengov-mcp-server` package is third-party and targets Socrata) - No deprecation policy, no Sunset/Deprecation headers, no SLA, despite two suites already shipping a superseded v1 - No published rate-limit quota, no 429 response, no Retry-After - No RFC 9457 problem details — errors are either a JSON:API `errors[]` array or a flat `{status, code, detail}` object