# Preview board transfer mappings

Compare source and destination custom-board columns before a duplicate or move. It suggests only unique compatible matches and reports unmapped fields and unsupported attachments; no rows are written. Body: `targetBoardId` (a board id or its `board-…` key) and an optional `mapping` {source column id: target column id}. Answers `mappings` (each with its `conversion` and `confidence`), `unmapped` (each with its `reason`) and `warnings`. It reads schemas only: a row's values and linked records are checked when the transfer runs — `post_boards_id_rows_rowId_transfer`, or the workflow preset `record.transfer_board` (sourceBoard, sourceRow, targetBoard, mode duplicate or move, mapping) — so a clean preview does not prove a given row will transfer.

Access class: `board:read`.

## Endpoint

`POST /v1/boards/{id}/transfer-preview`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| id | path | string | Yes |

## Request body

Content type: `application/json`.

```json
{
  "mapping": {},
  "targetBoardId": ""
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "mappings": [
      {
        "confidence": "string",
        "conversion": "string",
        "sourceColumnId": "",
        "sourceLabel": "string",
        "targetColumnId": "",
        "targetLabel": "string"
      }
    ],
    "unmapped": [
      "string"
    ],
    "warnings": [
      "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"
}
```
