By name: tallinn-open-data description: Query Tallinn city open data API and documentation for municipal datasets and city-level analysis workflows.
Tallinn Open Data
Use when
- You need Tallinn-specific municipal datasets.
- You need direct city API access for repeatable pulls.
Avoid when
- You need national cross-agency discovery first.
Inputs
- Table name, columns, filters, pagination.
Outputs
- API response dataset and query log.
Primary endpoints
- API root: https://avaandmed.tallinn.ee/
- Swagger UI: https://avaandmed.tallinn.ee/docs
- OpenAPI schema: https://avaandmed.tallinn.ee/openapi.json
- Data query endpoint pattern:
https://avaandmed.tallinn.ee/data/?table=...&columns=...&filters=...&page=...&per_page=...
Workflow
- Inspect table names and parameters from docs.
- Query
/data/with bounded filters/pagination. - Validate field types and missing values.
- Return cleaned municipal dataset.
Human setup (when needed)
- If table name is unknown, ask the user for the dataset reference from andmed.eesti.ee and then construct the query together.
Quality checks
- Respect API limits and timeout constraints.
- Keep query params in output metadata for reproducibility.
Access reality
- Public access type: API or structured endpoint access.
- Verification run: 2026-02-24.
- https://avaandmed.tallinn.ee/ (HTTP 200, text/html;, file links detected: 0)
- https://avaandmed.tallinn.ee/docs (HTTP 200, text/html;, file links detected: 0)
- https://avaandmed.tallinn.ee/openapi.json (HTTP 200, application/json, file links detected: 0)
Request contract
- Use the listed primary endpoints as authoritative entry points.
- If API/query parameters are only visible in-browser, preserve exact request URL, params, and headers in output metadata.
- If endpoint is UI-only, document click path and extraction method used.
Output schema expectations
- Keep at least: source URL, retrieval timestamp, publication/update date (if available), title/record label, and extracted governance-relevant fields.
- Preserve original field names when present in downloadable/API output.
Limits and caveats
- Confirm whether data is open-download, UI-only, or authenticated before claiming full access.
- Separate narrative/guidance text from measurable records.
Verification hooks
- Validate endpoint reachability and content type before extraction.
- Validate that each extracted claim is linked to a concrete source URL.