# Put records into a relationship

Adds up to 100 rows to one entity group. Answers 200 with a line per row: membership is EXCLUSIVE, so a record already in another relationship is refused individually with the sentence saying so while the rest of the batch lands.

Access class: `def:read`.

## Endpoint

`POST /v1/definitions/{key}/entity-groups/{groupId}/members`

## Parameters

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

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "role": "string",
    "rowIds": [
      "string"
    ]
  },
  "params": {
    ":groupId": "",
    ":key": "string"
  },
  "query": {}
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "changed": 1,
    "failed": 1,
    "requested": 1,
    "results": [
      {
        "changed": "string",
        "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"
}
```
