# Assign one person to many records

Puts ONE person in ONE role across many records in a single transaction — the bulk form of `put_definitions_key_rows_rowId_assignee_role`. It works on any page that has assignable people (deals, leads, submissions, merchants) and the page comes from the route, so the body carries no entity type. At most 100 ids; a bad role or a person holding no seat refuses the whole request, while a row id that names nothing is that row's own outcome and the batch carries on.

Access class: `def:read`.

## Endpoint

`POST /v1/definitions/{key}/rows/assignees`

## Parameters

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

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "assignee": "string",
    "ids": [
      "string"
    ],
    "role": "string"
  },
  "params": {
    ":key": "string"
  },
  "query": {}
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "failed": 1,
    "requested": 1,
    "results": [
      {
        "error": "string",
        "ok": "string",
        "rowId": ""
      }
    ],
    "succeeded": 1
  }
}
```

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