/v1/definitions/{key}/rows/{rowId}/submissionsList the form answers filed on a record
The FORM submissions filed against one record — NOT its lender submissions; a deal's sends to lenders are rows of the Submissions page (get_definitions_key_rows, params.key = "submissions", filtered by the deal). These are 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. Answers are masked for the caller exactly as the Responses tab masks them (get_forms_id_responses, docs/forms.md § 31): an answer filling a column your column access hides, an SSN/EIN no column you can see shows, an answer to a question the form no longer asks, or every answer of an application whose record is behind your row wall is left out of answers and named in withheld.
Access class: def:read.
Send request
Use the documented inputs to call this endpoint directly.
Parameters
Values are applied to the request and the example on the right.
Responses
the action's answer
{
"data": [
"string"
]
}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.
{
"error": "string"
}