29 Worklist
1 operation.
29.0.1 listWorklist
GET /api/worklist
List what is outstanding across a campaign — the findings raised against an organisation’s assets and the notes filed on its datasets — as one feed sorted by what changed most recently.
Why it exists. † List what is outstanding across a campaign — the findings raised against its organisation’s assets and the notes filed on its datasets — as one feed sorted by what changed most recently, so an engineer has a single answer to “what is outstanding here” instead of two screens.
Called by — components/workspaces/worklist-client.tsx
Reached from — /w/integrity/worklist
Merges the findings raised against an organisation’s assets with the notes filed on its datasets into one feed sorted by most recent activity. organizationId is required and scopes both halves; datasetId narrows notes only, since a finding has no first-class link to a dataset. Capped at 5000 rows (default 1000); truncated is true when the cap was reached.
Authentication: SupabaseAuth, CookieAuth
Returns — items · …meta · scope
Field names as the handler returns them; the source states no types for them.
Effect — reads equipment_damage_mechanisms · images · location_notes
Parameters
| Name | In | Required | Type | Notes |
|---|---|---|---|---|
organizationId |
query | no | string (uuid) | |
datasetId |
query | no | string (uuid) | |
limit |
query | no | integer |
Responses
| Status | Meaning | Body |
|---|---|---|
200 |
The merged, activity-sorted feed. | |
400 |
organizationId is missing or not a UUID, or datasetId is present and not a UUID. | Error |
401 |
Not signed in. | Error |
500 |
The database refused either half’s read for a reason the route could not classify. | Error |