Count the Triage queue
The numbers of the Triage rail and header for the queue filters of GET /api/v1/triage/findings: findings per stage, per saved view, per effective severity and per source, over the findings of your team’s active sources that you can see. Each facet ignores its own filter and applies the others (stage counts drop stage, view counts drop view, severity counts drop severity, source counts drop source_id and source_kind). Each number is counted up to 10,001: exact is false when more than 10,000 findings match, and the number reads as “10,000+”. partial is true when your team has more private GitHub repositories than one request checks, so some findings may be left out.
Headers
Query Parameters
A saved view of the queue. all: findings that are not closed. needs_decision: untriaged or verdict ready with no decision. critical_high: open findings whose effective severity is critical or high. in_fix: accepted findings being fixed. waiting: untriaged findings older than 7 days. snoozed: findings with an active snooze. Omit to list every stage.
all, needs_decision, critical_high, in_fix, waiting, snoozed Only findings whose latest triage or auto run reached one of these verdicts (Neo's disposition). A finding with no verdict, because it has no finished run or its run failed, matches none of them. Omit to match every finding.
7valid, need_more_info, duplicate, informative, not_applicable, spam, unknown Only open findings whose SLA target (counts sla) is overdue (past it) or due_soon (due within 7 days, not yet past). It narrows the page, count and every counts facet except sla, with the same predicate as counts.sla.past and counts.sla.due_7d; snoozed findings follow include_snoozed.
overdue, due_soon Response
The queue counts
The counts of GET /api/v1/triage/queue/counts. Sources with no matching finding are left out.

