Keys and access
Keys belong to your organization. After SeeGov grants government access, an organization administrator can open Organizations & Publications from the account menu to create or revoke its credentials. A sole authorized destination opens directly. With multiple destinations, select the destination first and select View settings. Use Switch organization or publication on a detail page to return to the chooser. The secret is shown once; SeeGov cannot retrieve it later. Contact SeeGov to change government access or recover organization administration.
Save a newly issued secret in your secret manager when it is shown. For rotation, create a replacement, update your integration, verify a request, then revoke the old key. Review and rotate keys when their creator leaves; keys remain owned by the organization. Never include credentials in support messages. Share only the response's requestId or X-Request-ID when diagnosing a failure.
Coverage is checked on every request and continuation page. The initial launch grant includes all available meeting history for each government SeeGov grants to the organization. The API represents that as an unbounded history interval; it describes access, not recording availability. Meeting-list filters intersect with the grant.
An existing meeting outside coverage returns 403 meeting_access_denied, with accessReason of government_coverage or history_coverage. Contact SeeGov about expanded access. This does not promise a paid upgrade will resolve the denial. A nonexistent meeting returns 404. A 401 means the credential is missing, invalid or revoked; a disabled organization or absent effective service gives 403 api_access_denied.
On 409 access_changed, refresh coverage and restart historical discovery with deduplication. Newly granted old meetings are not discoverable through a recent time checkpoint alone.
Last updated
Was this helpful?