Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
Permitting & land useConnector

OpenGov Permitting & Licensing integration

OpenGov Permitting & Licensing is a cloud system cities use for building permits, business licenses, code enforcement and other applications. Records move through approval steps handled by staff in different departments.

Request a demoAll connectors
Pre-built connector

OpenGov Permitting & Licensing

Tier
Pre-built connector
Category
Permitting & land use
Sign-in
OAuth 2.0 client credentials
Paging
next link

Vendor documentation ↗

§ Overview

What connecting OpenGov does.

SentraBridge reads changed records, record types, approval steps and users, creates records and updates approval steps. Paths come from third-party copies of OpenGov's specs, since its docs sit behind a developer login, so they are checked with the city's OpenGov contact before going live.

  • Records: Read changed records; create records and update their attributes.
  • Record types: Read type names and categories.
  • Approval steps: Read steps on a record and update their status.
  • Users: Read staff users' names and emails.
What SentraBridge can do with OpenGov Permitting & Licensing
resourcereadwritechanges onlyfields
Recordslist, read onecreate, updateyesID, Record number, Status, Record type, Address, Updated…
Record typeslist——ID, Name, Category
Approval steps on a recordlistupdate—ID, Step, Status, Completed
Userslist——ID, Email, First name, Last name
§ Use cases

What cities connect OpenGov for.

Permits to the open-data portal

Each night, changed OpenGov permits are upserted into a Socrata dataset residents and reporters can query.

Permits on a GIS layer

Issued permits are added to an ArcGIS layer for planning and the public permit map.

Fire review step from another system

When a fire department system finishes a plan review, the matching OpenGov approval step is marked complete.

Reporting table for finance

Records with fees are upserted into SQL Server for monthly revenue reports.

§ Examples

Flows that use OpenGov Permitting & Licensing.

Flow diagram: Publish OpenGov permits to the open-data portalNightly, upserts changed OpenGov permit records into a Socrata / Tyler Data & Insights dataset.Nightly at 3 amOn a scheduleChanged OpenGovrecordsGet records · OpenGovPublic fields onlyMap fieldsUpsert into the datasetSend records · Socrata
Publish OpenGov permits to the open-data portal · 4 steps · a real SentraBridge template
§ How it works

How to connect OpenGov

  1. 01Get accessAsk OpenGov for OAuth client credentials under the city's contract.
  2. 02Add the connectionConfirm the token URL and API paths with OpenGov.
  3. 03Preview real recordsSet the community variable to the city's OpenGov community name.
  4. 04Turn it onPreview records and record types before writing anything.
§ Often connected with

OpenGov and the rest of city hall.

Systems cities commonly connect with OpenGov, each with its own connector page.

§ FAQ

OpenGov integration questions

Does OpenGov have an API?

Yes. OpenGov offers an API for Permitting & Licensing to customers, with docs behind its developer login. SentraBridge signs in with OAuth client credentials.

How do I publish OpenGov permits to Socrata?

Read records changed since the last run, map the fields you want public, and upsert them by row ID into a Socrata dataset each night.

Are the OpenGov paths confirmed?

They come from third-party copies of OpenGov's specs. We check them against developer.opengov.com with your account before going live.

§ Next

Related connectors

Permitting & land useAccela Civic PlatformPermitting & land useTyler EnerGovOur productsCivicCA

Connect OpenGov Permitting & Licensing to the rest.

We'll set up a workspace with your systems in a sandbox and build your first flow with you.

Request a demoBrowse live examples