Subgraph
Return the filtered match count, plus the graph itself when under the cap.
total is always returned. When total > cap the response is {total, capped: true, courts} with no node/edge arrays (cheap — this drives the client's "narrow your filters" guard). When total <= cap the bounded node set and its induced cites edges are included.
outcomes and appeals ride along here and deliberately not on /graph/export. A verdict changes the moment a reviewer confirms it, and CorpusCacheControlMiddleware puts max-age=300, stale-while-revalidate=86400 on every successful GET under /authorities/ — which covers /graph/export and does not cover this POST. A verdict behind that cache would be stale for exactly the cases someone had just reviewed, which is the same reason the outcome is attached per search page rather than indexed into the Meilisearch document. The same holds for appeals: its status is derived from those verdicts, so it goes stale on the same click.
Request
- Base URL: https://api.casenode.ai
- URL: https://api.casenode.ai/authorities/graph/subgraph
- Auth: none declared
Request body
Example request
{
"cap": 500,
"filters": [
{
"field": "cited_by_min",
"value": "150"
}
],
"query": "burden of proof discrimination"
}Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.