# Record a board import run

Record an import somebody ELSE performed row by row, so it lands in the board's history and can be rolled back. `POST /v1/boards/import` records its own run and is what to reach for to actually import — use this only when the rows have already been written and you are reporting `{fileName, total, imported, failed, results}`. The row ids in `results` are stamped as this batch's, which is what makes the undo exact.

Access class: `board:write`.

## Endpoint

`POST /v1/boards/{id}/imports`

## Parameters

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

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "error": "string",
    "failed": 1.5,
    "fileName": "string",
    "imported": 1.5,
    "results": [
      "string"
    ],
    "total": 1.5
  },
  "params": {
    ":id": "string"
  },
  "query": {}
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "actorUserId": 1.5,
    "createdAt": "string",
    "failed": 1.5,
    "fileName": "string",
    "finishedAt": "string",
    "id": "",
    "imported": 1.5,
    "results": [
      "string"
    ],
    "standing": 1.5,
    "status": "string",
    "total": 1.5
  }
}
```

### 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"
}
```
