# Change a record's status

Moves one record to a status its page carries, with optional `notes`, and writes the move to the record's timeline in the same transaction — which is why this exists rather than patching the status cell. Re-picking the status the record already has is a no-op, not a refusal. A word the page does not carry, a word that has been archived, a page with no status column, and (on leads) a move the lifecycle forbids are each refused with a sentence saying so. Money boards refuse: their rows move by their own ledger action.

Access class: `def:read`.

## Endpoint

`POST /v1/definitions/{key}/rows/{rowId}/status`

## Parameters

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

## Request body

Content type: `application/json`.

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

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "archived_at": "string",
    "assignees": {},
    "cells": {},
    "createdBy": "string",
    "display": {},
    "externalId": "",
    "groupId": "",
    "id": "",
    "position": 1,
    "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"
}
```