# What a move needs first

What a deal would still need before it may move to `to` (a status or a stage): the missing columns keyed by column id, with each one's label, kind and the sentence the move would refuse with, plus whether the target asks for a reason. Ask it before acting on a status menu, so the person fills the gap instead of reading a refusal.

Access class: `def:read`.

## Endpoint

`GET /v1/definitions/{key}/rows/{rowId}/transition/requirements`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| rowId | path | string | Yes |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "asks": [
      {
        "column": "string",
        "kind": "string",
        "label": "string",
        "prompt": "string",
        "required": "string"
      }
    ],
    "missing": [
      {
        "because": "string",
        "column": "string",
        "kind": "string",
        "label": "string"
      }
    ],
    "reasonRequired": true,
    "stage": "string",
    "status": "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"
}
```