# List a deal's submissions to lenders

The FORM submissions filed against one record — the answers a merchant or a person actually typed into a form, newest first, in the same shape `get_forms_id_submissions` answers. That route is addressed by FORM, so this is the only way to ask which submission belongs to THIS record, which is what a record's Application tab needs. Mind the noun: `submissions` on the POST under this row (`post_definitions_key_rows_rowId_submissions_prepare-send`) means LENDER submissions, a different thing entirely. A record nobody filled a form for answers an empty list; a record this workspace cannot see answers 404. `limit` narrows it.

Access class: `def:read`.

## Endpoint

`GET /v1/definitions/{key}/rows/{rowId}/submissions`

## 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": [
    "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"
}
```