# Create a record group on a page

Makes an EMPTY record group on a page, from `name` (required), `description` and `colour` — that it can be empty is the whole difference from a status. It lands last in the board's order. A name already used on this page is a 409, and the check is case-blind, so 'Q4 Push' and 'q4 push' collide. Put records in with `post_definitions_key_groups_groupId_rows`.

Access class: `def:read`.

## Endpoint

`POST /v1/definitions/{key}/groups`

## Parameters

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

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "colour": "string",
    "description": "string",
    "name": "string"
  },
  "params": {
    ":key": "string"
  },
  "query": {}
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "colour": "string",
    "createdAt": "string",
    "createdByUserId": 1,
    "description": "string",
    "id": "",
    "memberCount": 1,
    "name": "string",
    "position": 1,
    "statusGroup": "string",
    "updatedAt": "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"
}
```