---
title: "List data remediation tasks"
method: GET
path: "/v1/data/tasks"
tags: ["Data Quality"]
---

# List data remediation tasks

`GET /v1/data/tasks`

## Request

- Base URL: `https://api.gunspec.io`
- URL: `https://api.gunspec.io/v1/data/tasks`
- Auth: one of:
  - none
  - API key in header `X-API-Key`
  - HTTP bearer

The work generated from what the quality checks find, and where each item has got to.

Keyless, on the same reasoning as the gap report: a measurement nobody can see being acted on is a measurement. A task reveals nothing about the catalog that `/v1/data/gaps` does not.

**What this deliberately does not carry** is anything identifying the worker: which agent or person holds a task (`assignedTo` says only whether it is the platform's agent or a person), what value they proposed, and the note they closed it with. An unreviewed answer published beside a record reads as a fact about that record. A proposal becomes public by being accepted into the catalog, which is the surface that already carries values.

States: `open` (queued), `claimed` (allocated to a worker), `in_progress` (being worked), `resolved` (finished, or the finding disappeared), `unverifiable` (searched and not findable), `not_a_fault` (the check was wrong about this record).

No API key required.

## Query parameters

- `status` 'open' | 'claimed' | 'in_progress' | 'resolved' | 'unverifiable' | 'not_a_fault'
- `entity` 'manufacturers' | 'firearms' | 'calibers' | 'attachments' | 'ammunition'
- `check` string
- `field` string
- `subject` string
- `q` string
- `kind` 'gap' | 'contradiction' | 'vocabulary' | 'asset' | 'verify' | 'report'
- `stage` 'queued' | 'working' | 'proposed' | 'accepted'
- `checks` string
- `state` 'open' | 'closed'
- `closer` 'redback' | 'redback_accepted' | 'team'
- `include` 'research'
- `limit` integer
- `page` integer

## Response `200`

List data remediation tasks

- object
  - `success` boolean, required: Always true on a successful response. Every error carries `false` and an `error` object instead.
  - `data` object, required: The response payload.
    - `total` integer: How many tasks match.
    - `page` integer: This page.
    - `perPage` integer: Tasks per page.
    - `tasks` object[]: Most recently seen first; with `state=closed` or `closer`, most recently closed first.
      - `taskKey` string, required: Stable id, derived from the finding rather than assigned, so the same finding is the same task tomorrow.
      - `number` integer, nullable, required: The task's number; `/v1/data/tasks/{number}` loads it.
      - `research` object: With `include=research` only: what a researcher needs, read from the task. Never its result.
        - `describes` string, nullable, required: The check's rule and this finding's own line.
        - `field` string, nullable, required: The record field it concerns.
        - `rules` string[], required: The steps to resolve it.
        - `evidence` object, nullable, required: What the check measured, or the values removed as invented (never to be reused).
        - `record` object, nullable, required: The record's fields as a reviewer is handed them.
        - `alreadyCites` string[], required: The pages the record already cites.
        - `key` string, nullable, required: The finding's own key within its check: the record and field, or a cited host.
        - `currentValue` unknown, required
        - `affected` string[], required: Every record the finding covers, as `<kind>:<id>`.
      - `kind` 'gap' | 'contradiction' | 'vocabulary' | 'asset' | 'verify' | 'report', required: What the asset is: `silhouette`, `render`, `photo`, `schematic`, `model`. `/v1/firearms/{id}/media/{selector}` addresses an asset by this.
      - `entity` string, required: Which catalog.
      - `subject` string, required: The record, or for a vocabulary task the value being decided.
      - `finding` string, nullable, required: The check id or field this came from.
      - `status` 'open' | 'claimed' | 'in_progress' | 'resolved' | 'unverifiable' | 'not_a_fault', required: Production status, one of `in_production`, `discontinued`, `out_of_production`, `in_service`, `limited_production`, `prototype`. Discontinued records are kept deliberately: a rifle built in 2004 wears parts nobody sells today.
      - `records` number, required: How many records this would fix. One for most; a vocabulary decision covers every record holding that spelling.
      - `openedAt` string, required: When the finding was first seen.
      - `startedAt` string, nullable, required: When a worker began, or null.
      - `closedAt` string, nullable, required: When it closed, or null.
      - `hasResult` boolean, required: Whether a worker has filed a conclusion. Never what it says.
      - `assignedTo` 'redback' | 'staff' | 'null', nullable, required: Which kind of worker holds the task: `redback`, the platform's agent, or `staff`, a person. Null when nobody does. Never which agent or which person.
      - `closedReason` 'finding_gone' | 'worked' | 'by_hand' | 'null', nullable, required: Why a closed task closed, as a code: `finding_gone` (the check no longer finds it, because the record was corrected), `worked` (a worker filed a conclusion) or `by_hand` (closed without one). Null while open. Never the note it was closed with.
      - `closer` 'redback' | 'redback_accepted' | 'team' | 'null', nullable, required: Who closed it, as a kind: `redback` (the platform's agent filed a conclusion nobody has judged yet), `redback_accepted` (a person accepted what the agent filed) or `team` (a person worked or closed it, or corrected the record so the check no longer finds it, which `closedReason` then says). Null while open. Never which agent or which person.
  - `pagination` Pagination: Page-size is reported under both `per_page` (matching the request parameter) and `limit` (retained for existing integrations). They always carry the same value. `total` and `totalPages` are omitted for Explorer and anonymous callers.
    - `page` integer, required: The page this response is, 1-based.
    - `per_page` integer, required: Page size. Same value as `limit`.
    - `limit` integer, required: Page size. Alias of `per_page`.
    - `total` integer: Total records matching the query across every page.
    - `totalPages` integer: How many pages the result set spans at the current `per_page`.

## Other responses

- `400`: Validation error
- `429`: A limit was reached. `RATE_LIMITED` is the per-minute limit: wait `Retry-After` seconds (a minute) and retry. `DAILY_CAP_EXCEEDED` is the plan's daily limit, per key: nothing will be served until the counters return to zero at midnight UTC. `MONTHLY_CAP_EXCEEDED` is the plan's monthly allowance, for the whole account: nothing will be served until midnight UTC on the first of next month, or until the plan changes. For both, `Retry-After` is the seconds until then and `error.resetsAt` says when as an instant. Calls made after a refusal are refused too and do not spend the month, and a free key that keeps calling is paused, so stop at the first one and resume at the reset.
- `500`: Internal server error

---

[API](https://skmtc.dev/gunspec/apis/gunspec-io-api.md) · [All operations](https://skmtc.dev/gunspec/apis/gunspec-io-api/llms.txt) · [OpenAPI document](https://skmtc.dev/gunspec/apis/gunspec-io-api/revisions/f2e974d8b05c?raw)