OpenGov Record Guests API
Record Guests are additional users who need visibility into the permit/license process. This could includecontractors, architects, property owners, or other stakeholders who need to track the application's progress,receive updates, or help manage the application. For example, a homeowner (Applicant) might add theircontractor (Guest) to a building permit to help upload revised plans or respond to inspector comments.A record can have up to 10 Guests. The Applicant or any employee user can add Guests to a Record.
OpenGov Record Guests API is one of 102 APIs that OpenGov publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Record Guests. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.
This API exposes 4 operations across 2 paths. It is described by OpenAPI 3.2.0, at version v2.
Requests are made against a single base URL, https://api.plce.opengov.com/plce.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
OpenGov Record Guests API declares
4 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basicHttpAuthentication).
It accepts HTTP bearer tokens (JWT) (bearerAuth).
It supports OpenID Connect (auth0Prod) discovered at https://accounts.viewpointcloud.com/.well-known/openid-configuration.
It supports OpenID Connect (auth0Dev) discovered at https://login.vpctest.com/.well-known/openid-configuration.
By default, every request must be authenticated.
basicHttpAuthentication— Basic HTTP AuthenticationbearerAuth— The OpenGov Permitting & Licensing API is authenticated using the OAuth2 Client Credentials flow. Access tokens are provided as a bearer token Authorization he…auth0Prod— The OpenGov Permitting & Licensing API is authenticated using the OAuth2 Client Credentials flow. Access tokens are provided as a bearer token Authorization he…auth0Dev— The OpenGov Permitting & Licensing API is authenticated using the OAuth2 Client Credentials flow. Access tokens are provided as a bearer token Authorization he…
Paths & Operations 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Record Guests are additional users who need visibility into the permit/license process. This could include contractors, architects, property owners, or other stakeholders who need…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from OpenGov 12
Other APIs OpenGov publishes across the network.
This is an independent, third-party profile of OpenGov Record Guests API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.