# Change definitions key rows rowId

MERGES the given cells into one record and answers the whole row: a column the body does not mention keeps its value, so a single-cell edit cannot blank the rest of the record with a stale copy. Use `post_definitions_key_rows_rowId_status` for the status word — it has its own door because it also writes the move to the record's timeline — and `patch_definitions_key_cells` for the same change across many rows. Money-board rows are refused; an unknown row is a 404.

Access class: `def:read`.

## Endpoint

`PATCH /v1/definitions/{key}/rows/{rowId}`

## Parameters

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

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "cells": {}
  },
  "params": {
    ":key": "string",
    ":rowId": ""
  },
  "query": {}
}
```

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "cells": {
      "<uuid-2>": "string",
      "<uuid-3>": "string",
      "<uuid-4>": "string"
    },
    "id": "",
    "position": 1.5,
    "source": "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"
}
```