# Read a record's document-processing status

The newest processing job on one record, with its event feed in order and the documents it covered, in one query. A record nobody has processed answers a ZERO job with an empty status rather than a 404, so 'not processed' and 'bad id' stay distinguishable. What a job actually extracted is read per tab: bank-statements, tax-returns, credit-reports, or `financials` for the rollup.

Access class: `def:read`.

## Endpoint

`GET /v1/definitions/{key}/rows/{rowId}/processing`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| rowId | path | string | Yes |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "documents": [
      {
        "at": "string",
        "attemptNo": 1.5,
        "contentSha256": "string",
        "documentType": "string",
        "extractions": [
          "string"
        ],
        "fileId": "",
        "fileName": "string",
        "id": "",
        "outcome": "string",
        "reason": "string"
      }
    ],
    "events": [
      "string"
    ],
    "externalJobId": "",
    "findings": [
      "string"
    ],
    "finished": true,
    "id": "",
    "idempotencyKey": "string",
    "requestedAt": "string",
    "requestedBy": "string",
    "status": "string"
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```
