> 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.md).

# Meetings API

The SeeGov Meetings API is our public, customer-facing API. It lets approved organizations retrieve full meeting transcripts alongside SeeGov's analysis: detected agenda items with metadata such as timing, votes and assessments, and summaries of individual moments, where available. Organizations can also poll for newly available meetings. Access is limited to the governments and meeting-date history SeeGov has granted your organization. Contact SeeGov to arrange access.

The base URL is `https://seegov.org/api/v1`. Use `Authorization: Bearer <organization key>`. Read the key from your secret manager or environment; never put it in a URL, source control, or logs.

The API returns JSON with `data` and `requestId`. Public fields and parameters use camelCase. Only government and meeting lists have a `page` object. Transcript, agenda and moment responses contain the entire meeting resource. Default list size is 100, maximum 200. Unknown or repeated parameters are errors.

1. Review your coverage with `GET /api/v1/governments`.
2. List ready meetings with `GET /api/v1/meetings`.
3. Fetch `/api/v1/meetings/{meetingId}/transcript` for each selected ID.
4. Use `?granularity=word` for stored word timestamps, or `?include=speakers` for stored names/types. These options can be combined.
5. Fetch `/api/v1/meetings/{meetingId}/agenda-items` and `/api/v1/meetings/{meetingId}/moments` for stored agenda analysis and moment summaries.

## Link reporters back to Backstage

Every meeting object includes `links.seegov`, the meeting's authenticated Backstage URL. Use that value when your integration identifies a meeting that a reporter should review.

To focus a specific moment, append its returned `id` as the `moment_id` query parameter. For example:

`https://seegov.org/meetings/{meetingId}?moment_id={momentId}`

Build the query parameter with your URL library rather than concatenating unescaped values. The recipient must be signed in to Backstage and have access to the meeting. The link opens the meeting with that moment selected and the player positioned at its start; it does not start playback automatically.

See [historical import and polling](/api/import-and-polling.md), [keys and access](/api/keys-and-access.md), and [missing data, notices and retries](/api/data-and-errors.md).

The [API reference](/api/reference.md) defines the exact schemas and parameters. You can also download the OpenAPI contract from that page.

Clients should ignore unknown response fields and tolerate new speaker-type strings. Breaking changes use a new path-major version. The default retirement policy is 90 days' notice and an agreed date for each active customer, except urgent security/access enforcement; this is not a contractual SLA.


---

# 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.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.