authorities

Get Authority Impact

What later courts have cited this judgment FOR, if we have derived it.

A different question from /summary, and one the judgment cannot answer. A summary is read out of the case; this is read out of the 2.39M citation edges around it, so the two have different lifetimes and live in different tables. Nothing here is a claim about whether the case is still good law: treatment is a separate axis and relationship_type is 2,389,410 bare cites, so we do not hold it.

Absent is 200 with an empty object, not 404, for exactly the reason the summary endpoint gives: having no record is the ordinary answer for almost every case, and 404 would make the normal path an error that every case page load would log. A 404 here means the AUTHORITY does not exist.

The method gate mirrors /summary's and is here rather than in each caller because this endpoint is what the case viewer reads. It is deliberately strict about a value that only has one member today: a second writer would have to be added on purpose, and adding it is the moment to decide whether it is fit to serve.

⚠ Unlike /summary, absence here must NEVER withhold a page. _HAS_SUMMARY in indexable.py exists because a case page with template prose on it is worse than one without; a case page with no impact section is simply a case page, so there is no equivalent flag and there should not be one.

get/authorities/{authority_id}/impact

Request

  • Base URL: https://api.casenode.ai
  • URL: https://api.casenode.ai/authorities/{authority_id}/impact
  • Auth: none declared

Path parameters

authority_idstring required

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.