> 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/import-and-polling.md).

# Historical import and polling

Start `GET /api/v1/meetings` without `availableSince` to discover history across all covered governments. Optional `governmentId`, `meetingDateFrom` and `meetingDateTo` narrow the scan. Meeting dates are inclusive `YYYY-MM-DD` values.

Follow `page.nextUrl` unchanged until null. Before advancing page progress, durably queue its meeting IDs. Fetch the transcript, agenda items, and moments you need from that queue, and record completion only after saving each response. Retry failed resources independently so one failure does not block other meetings. Deduplicate by meeting ID and resource, and keep import progress on durable storage separate from the downloaded data.

On the final page, save `page.nextAvailableSince`. **This is the value to send as `availableSince` on the next scan, not the time to send the request.** Poll about every five minutes with the same filters. Even an empty final page returns a checkpoint. Each scan has a fixed `scanUntil` boundary, and the next checkpoint includes a five-minute overlap; repeat IDs are expected. Ignore resources you have already imported successfully unless you are refreshing their contents.

Each transcript GET returns every original phrase. Phrase start/duration are seconds on the media timeline, including lead-in. Word mode preserves that same phrase text and timing and adds words; do not reconstruct original text from words. Phrase IDs and speaker labels can change during reprocessing and are not cross-meeting identities.

Re-fetching a known meeting returns its current data. Corrections and reruns do not change first availability. This is not an update, deletion or exactly-once feed. Retry known temporarily unavailable IDs and periodically reconcile through historical scans. No immutable snapshot spans multiple resources.

Cursors expire after seven days. Restart from the last completed checkpoint, or restart historical import if there is none. After access expansion, rescan history; an old time checkpoint cannot reveal newly granted older meetings.

Keep separate checkpoints for each organization and filter set. Follow continuation URLs on the same API origin; never forward your key to another host. Restrict access to downloaded data and import progress. Start with sequential requests and use at most two concurrent requests, honoring `Retry-After` and the [request limits](https://docs.seegov.org/api/data-and-errors.md).


---

# 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/import-and-polling.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.
