# Read where file types' results go

The workspace's result mappings: for each file type (documentType, the app's document word or a custom_<slug> type) and board (definitionId), which extracted field goes to which column — on the same row (target same_row) or on the row a relation column links to (linked_row, relationColumnId) — narrowed to one file column when fileColumnId is set, with its updateRule (fill_empty writes only into an empty cell, review holds the value for a person, overwrite replaces a value unless another document wrote it). status is active, or needs_attention with problem column_missing, column_changed, relation_missing or file_column_missing when the board changed since; such a mapping writes nothing. ?documentType= narrows to one file type. Any seat.

Access class: `workspace`.

## Endpoint

`GET /v1/workspace/processor/result-mappings`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| documentType | query | string | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": [
    "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"
}
```
