---
title: "Get Overview Summary"
method: GET
path: "/snapshots/{snapshot_id}/overview-summary"
tags: ["dashboard"]
---

# Get Overview Summary

`GET /snapshots/{snapshot_id}/overview-summary`

The full OSS repowise 0.22.0 ``OverviewSummaryResponse`` — one call that
drives the whole repo Overview page (repo meta, stat strip + deltas, health
block + the two co-equal pillars + history, languages, the typed attention
list, onboarding targets, top hotspots, recent decisions, savings, sync).

Mirrors ``repowise.server.routers.overview`` field-for-field but every value
is computed from the JSON artifacts the Modal indexer uploads instead of SQL
(see ``app/services/overview_summary_service.py``).

Served from a two-tier cache (per-process LRU → durable Postgres row, see
``overview_cache_service``), keyed by snapshot + content version, since the
aggregate is expensive to compute and deterministic per snapshot version. A
cache miss computes it and fills both tiers. A fresh repo / a snapshot
indexed before the health layer degrades to a valid zeroed shape so the page
renders its empty state rather than 404-ing (that shape is not cached).

## Path parameters

- `snapshot_id` string, required

## Response `200`

Successful Response

- object

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/repowise/apis/repowise-hosted-api.md) · [All operations](https://skmtc.dev/repowise/apis/repowise-hosted-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/repowise/repowise-hosted-api/revisions/40167ba9ab58/schema)