---
title: "Get Authority Summary"
method: GET
path: "/authorities/{authority_id}/summary"
tags: ["authorities"]
---

# Get Authority Summary

`GET /authorities/{authority_id}/summary`

## Request

- Base URL: `https://api.casenode.ai`
- URL: `https://api.casenode.ai/authorities/{authority_id}/summary`
- Auth: none declared

The generated case_summary record for an authority, if one exists.

**An absent summary is 200 with an empty object, not 404.** 2,976 of
348,212 authorities have one this endpoint will serve, so "there isn't one"
is the ordinary answer for essentially every case page. Returning 404 would
make the normal path an error: the client would have to treat a successful,
correct response as a failure, and every case page load would log one.

Two things make a record unservable, and both read as absence rather than
as an error, because from a reader's side they are the same fact -- there is
no summary to show. A record is withheld if it is `stale` (its anchors point
into a parse the judgment no longer has) or if it is heuristic template
output rather than a model's writing. 15,132 records are the latter.

A 404 here means the AUTHORITY does not exist, which is a different fact and
the only one worth erroring on. The same quarantine gate as every other
authority read applies, so a case this API will not show is not-found rather
than summary-less.

`case_summaries_current` picks the newest run per authority. Older runs stay
in `case_summaries` and are not served: comparing generations is a review
job, not something to hand a reader.

## Path parameters

- `authority_id` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/casenode/apis/casenode-api.md) · [All operations](https://skmtc.dev/casenode/apis/casenode-api/llms.txt) · [OpenAPI document](https://skmtc.dev/casenode/apis/casenode-api/revisions/5b2883d19661?raw)