> For the complete documentation index, see [llms.txt](https://docs.seegov.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seegov.org/api/keys-and-access.md).

# Keys and access

Keys belong to your organization. After SeeGov enables its API 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 the organization's package or coverage, enable API access, or recover organization administration. Payment or evaluation alone does not enable the API.

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 API uses the credential's organization's full-meeting coverage and history; it does not combine access from a reporter's other organizations or personal list. Interactive research openings in Backstage do not expand API coverage. API reads do not consume the interactive research allowance.

Read `historyIntervals` from `GET /api/v1/governments` rather than assuming all-history access. Enforced intervals have `precision: timestamp`, an inclusive `from`, and a `to` boundary controlled by `endInclusive`. UTC timestamps are authoritative; the date-only `meetingDate` is for display. Local evaluation uses a rolling three-calendar-month window. Qualifying Local service includes its earned periods and preserves gaps; Regional and Enterprise include all available history for covered governments. Legacy date intervals, when returned, have inclusive boundaries. Intervals describe access, not recording availability. Meeting-list filters intersect with that access.

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.seegov.org/api/keys-and-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
