---
title: "List Report history"
method: GET
path: "/reports/{report-id}/history"
tags: ["reports"]
---

# List Report history

`GET /reports/{report-id}/history`

## Request

- Base URL: `https://api.withpersona.com/api/v1`
- URL: `https://api.withpersona.com/api/v1/reports/{report-id}/history`
- Auth: HTTP bearer

Retrieves the history of an existing Report, including runs and actions. See [Pagination](https://docs.withpersona.com/pagination) for more details about handling the response. Results are returned in reverse chronological order, with the most recently created objects first.

## Path parameters

- `report-id` string, required

## Query parameters

- `page` ReportsReportIdHistoryGetParametersPage
  - `after` string: Object ID for pagination cursor
  - `before` string: Object ID for pagination cursor
  - `size` number, double: Limit on the number of objects returned

## Headers

- `Key-Inflection` 'camel' | 'kebab' | 'snake'
- `Idempotency-Key` string
- `Persona-Version` '2026-09-29' | '2025-12-08' | '2025-10-27' | '2023-01-05' | '2022-09-01' | '2021-08-18' | '2021-07-05' | '2021-02-21' | '2020-05-18': Server API version. More info on versioning can be found [here](https://docs.withpersona.com/versioning).

## Response `200`

This endpoint returns a history array containing report runs and actions.

- ReportsListReportHistoryResponse200
  - `data` ReportHistoryItems[], required: The history of runs and actions for a report
    - union
      - object: A run entry in the report history
        - `type` 'run', required: Discriminator value: run
        - `id` string: The unique identifier for this history entry
        - `run-type` string, required: The type of run Possible values: - manual - scheduled Do not assume this is a static enumeration; Persona may add new values in the future without a versioned update.
        - `scheduled-date` string, date: The date the report is scheduled to run on
        - `completed-at` string, date-time, nullable: When the run was completed
        - `matches` integer, nullable: The number of matches found (only present if the run is completed)
      - object: A dismissal entry in the report history
        - `type` 'dismiss', required: Discriminator value: dismiss
        - `id` string: The unique identifier for this history entry
        - `created-at` string, date-time, required: When the dismissal was created
        - `creator-name` string, required: The name of the user that dismissed the report
      - object: A pause entry in the report history
        - `type` 'pause', required: Discriminator value: pause
        - `id` string: The unique identifier for this history entry
        - `created-at` string, date-time, required: When the report was paused
        - `creator-name` string, required: The name of the user that paused the report
      - object: A resume entry in the report history
        - `type` 'resume', required: Discriminator value: resume
        - `id` string: The unique identifier for this history entry
        - `created-at` string, date-time, required: When the report was resumed
        - `creator-name` string, required: The name of the user that resumed the report
      - object: A review entry in the report history
        - `type` 'review', required: Discriminator value: review
        - `id` string: The unique identifier for this history entry
        - `created-at` string, date-time, required: When the review was created
        - `creator-name` string, required: The name of the user that reviewed the report
  - `links` ReportsReportIdHistoryGetResponsesContentApplicationJsonSchemaLinks, required: Pagination links for navigating through the history
    - `prev` string, nullable, required: URL to the previous page of results
    - `next` string, nullable, required: URL to the next page of results

## Other responses

- `400`: The request was unacceptable, often due to invalid parameters.
- `401`: An invalid API key was provided.
- `403`: The given API key doesn’t have permissions to perform the request or a quota has been exceeded.
- `404`: The requested resource doesn’t exist.
- `429`: Your organization’s rate limit has been exceeded. We recommend an exponential backoff on requests.

---

[API](https://skmtc.dev/withpersona/apis/withpersona-4.md) - [All operations](https://skmtc.dev/withpersona/apis/withpersona-4/llms.txt) - [OpenAPI document](https://skmtc.dev/withpersona/apis/withpersona-4/revisions/2eddd7dae374?raw)