# Read a record's activity feed

One record's own timeline, newest first: who did what to it and when, with the before-and-after values on an edit. `limit` narrows it. Columns this caller's column policy hides are stripped out of the entries too, so a locked column's history is not readable through the feed. Any record page; for just the status ladder, `get_definitions_key_rows_rowId_status-history` is this same feed filtered.

Access class: `def:read`.

## Endpoint

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

## 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": [
    {
      "action": "string",
      "actorKind": "string",
      "actorUserId": 1.5,
      "createdAt": "string",
      "detail": {
        "account_id": "",
        "columns": [
          "string"
        ],
        "definition_id": "",
        "definition_key": "string",
        "entity_group_id": "",
        "name": "string",
        "role": "string",
        "scope": "string",
        "script_id": 1.5,
        "status": "string",
        "version": 1.5
      },
      "entityKind": "string",
      "entityRowId": "",
      "id": 1.5,
      "requestId": ""
    }
  ]
}
```

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