snapshots.triageResults.list
List published triage results for a completed snapshot.
The response contains one result per team and driver pair. Each result includes the team lead’s selection and comment, the team’s driver score in this snapshot, and the score in the comparison snapshot.
Facts
| Method | GET https://api.getdx.com/snapshots.triageResults.list |
| Required scope | snapshots:read |
Arguments
Required arguments
| Name | Type | Description |
|---|---|---|
token |
Token |
Auth token passed in the Authorization: Bearer HTTP header. |
snapshot_id |
Text |
ID of a completed snapshot belonging to the account. |
Optional arguments
| Name | Type | Description |
|---|---|---|
team_ids |
Array<Text> |
Comma-separated team IDs. Each team must be represented in the snapshot. Includes descendants in the snapshot hierarchy. |
snapshot_team_ids |
Array<Text> |
Comma-separated snapshot team IDs. Each must belong to the snapshot. Includes descendants. |
selection |
Array<Text> |
Comma-separated selections to include: keep_monitoring, make_improvements, or needs_support. |
Filtering behavior
With no filters, results cover every team in the snapshot. When both team_ids and snapshot_team_ids are supplied, the selected subtrees are intersected. Disjoint selections match no teams.
This method does not accept group_ids, branch_ids, or attribute_ids. Triage results belong to a team, so population filters that cut across teams do not apply.
Results are not paginated. They are ordered by team name, then driver name.
Example request
curl -X GET 'https://api.getdx.com/snapshots.triageResults.list?snapshot_id=MjUyNbaY&selection=needs_support' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer xxxx-xxxxxxxxx-xxxx'
Example response
This example uses an account minimum response threshold of 3.
{
"ok": true,
"filters": {
"snapshot": {
"id": "MjUyNbaY",
"scheduled_for": "2026-08-02",
"completed_at": "2026-08-16T14:00:00.000Z",
"completed_count": 48,
"total_count": 60
},
"comparison_snapshot": {
"id": "MjQ4Nxyz",
"scheduled_for": "2026-05-03",
"completed_at": "2026-05-17T14:00:00.000Z"
},
"selection": ["needs_support"],
"teams": [],
"snapshot_teams": []
},
"triage_results": [
{
"team": {
"id": "NTA1ODI",
"snapshot_team_id": "NTIxNDc",
"name": "Platform"
},
"driver": {
"id": "MTQ2",
"name": "Ease of release",
"audience": "dev"
},
"selection": "needs_support",
"selection_label": "Needs support",
"comment": "Release pipeline flakiness is blocking the team. Need platform help.",
"carried_over": false,
"submitted_by": {
"id": "NTEyMDUw",
"name": "Alex Lee",
"email": "alex.lee@example.com"
},
"updated_at": "2026-08-20T16:42:10.000Z",
"score": 42,
"hidden": false,
"previous_score": 61,
"previous_hidden": false,
"score_change": -19
}
]
}
Response fields
| Field | Type | Description |
|---|---|---|
ok |
Boolean |
Whether the request succeeded. |
filters |
Object |
The snapshot, comparison snapshot, and applied filters. |
triage_results |
Array<Object> |
Triage results for the requested teams. |
Filters object
| Field | Type | Description |
|---|---|---|
snapshot |
Object |
id, scheduled_for (YYYY-MM-DD), completed_at (ISO 8601), completed_count, and total_count. Counts reflect the applied team filters. |
comparison_snapshot |
Object or null |
id, scheduled_for, and completed_at of the snapshot that previous_score comes from. null when there is no earlier snapshot. |
selection |
Array<Text> |
Selected values from the selection argument; empty when not filtered. |
teams |
Array<Object> |
Selected teams, each with id and name; empty when not filtered. |
snapshot_teams |
Array<Object> |
Selected snapshot teams, each with id and name; empty when not filtered. |
The comparison snapshot is the previous snapshot, or the one before that when the account is configured to compare against two snapshots ago.
Triage result object
| Field | Type | Description |
|---|---|---|
team |
Object |
id (team ID), snapshot_team_id, and name as it was in the snapshot. |
driver |
Object |
id, name, and audience. |
selection |
Text |
keep_monitoring, make_improvements, or needs_support. |
selection_label |
Text |
Display label: Keep monitoring, Make improvements, or Needs support. |
comment |
Text or null |
The team lead’s comment. null when the token cannot view it. See comment visibility. |
carried_over |
Boolean |
true when the selection was copied forward from the comparison snapshot and no one has reviewed it in this snapshot yet. |
submitted_by |
Object or null |
id, name, and email of the person who submitted the result. null when carried_over is true. |
updated_at |
Text |
When the result was last changed (ISO 8601). |
score |
Integer or null |
The team’s score for this driver in the snapshot. null when hidden. |
hidden |
Boolean |
Whether score is suppressed by the account’s minimum response threshold. |
previous_score |
Integer or null |
The team’s score for this driver in the comparison snapshot. null when hidden or when there is no comparison data. |
previous_hidden |
Boolean |
Whether previous_score is suppressed by the threshold. false when there is no comparison data. |
score_change |
Integer or null |
score minus previous_score. null when either score is null. |
Scores include answers from the team’s descendants in the snapshot hierarchy. They match the scores shown in the triage view in DX.
Comment visibility
Organization API keys can read every comment.
A personal access token receives every result, but comment is null unless the token’s user is a Snapshot Admin or Workspace Admin, submitted the result, or is a member or DRI of the result’s team or one of its parent teams.
Privacy and missing data
A score is hidden when the number of rated answers to that driver from the team is below the account’s minimum response threshold. score and previous_score are evaluated separately, each against its own answer count.
When there is no comparison snapshot, or the team has no answers in it, previous_score is null and previous_hidden is false. Use previous_hidden to tell a withheld score from a missing one.
Errors
Check ok in every response. When it is false, read error and any error_details.
| Field | HTTP status | Description |
|---|---|---|
not_authed |
401 |
The authentication token is missing or invalid. |
not_authorized |
403 |
The token does not have access to this method, including the required snapshots:read scope. |
invalid_arguments |
400 |
snapshot_id is missing or malformed, a team ID is invalid or not in the snapshot, or selection has an unknown value. error_details identifies the argument. |
not_found |
404 |
The snapshot is unknown, belongs to another account, is deleted, or is not completed. |