---
title: "Get Report Schedule Runs"
method: GET
path: "/reports/scheduled-reports/{scheduledReportId}/runs"
tags: ["reports"]
---

# Get Report Schedule Runs

`GET /reports/scheduled-reports/{scheduledReportId}/runs`

Use this endpoint to get a list of instances for a scheduled report by it's unique identifier. If the scheduled report requested is not available the response will be a Not Found error. If the scheduled report requested hasn'run yet the response will be an Empty response.

## Path parameters

- `scheduledReportId` string, uuid, required

## Query parameters

- `pageSize` integer
- `pageStartIndex` integer

## Response `200`

OK

- ReportInstanceCollection — Base structure for all paginated collection responses. This provides consistent pagination metadata across all collection endpoints.
  - `count` integer — The total number of items available across all pages. Use this to calculate the total number of pages available.
  - `pageSize` integer — The number of items per page in this response. This reflects either your requested page size or the default value.
  - `pageStartIndex` integer — The starting index of this page of results. Use with pageSize to track your position in the overall result set.
  - `items` ReportInstance[]
    - `reportId` string — The unique identifier of the report instance.
    - `date` string, date-time — The generation of the report date and time in ISO 8601. https://en.wikipedia.org/wiki/ISO_8601
    - `runInstanceId` string, uuid — The unique identifier of Report Recipient Instance.
    - `recipientsCount` integer — The amount of recipients within the scheduled report instance

## Other responses

- `204` — No Content
- `400` — Bad Request - The server cannot process the request due to a client error. Common causes: - Invalid request format - Missing required fields - Validation errors in the request data
- `401` — Unauthorized - Authentication is required or has failed. Common causes: - Missing API key - Invalid API key - Expired or deactivated API key
- `404` — Not Found - The requested resource does not exist. Common causes: - Invalid subscription ID - Subscription has been deleted - URL path contains typos or incorrect values
- `416` — Range Not Satisfiable - The requested page of results is not available. Common causes: - pageStartIndex is beyond the available data range - Invalid pagination parameters

---

[API](https://skmtc.net/acculynx/apis/acculynx-api-v2.md) · [All operations](https://skmtc.net/acculynx/apis/acculynx-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/acculynx/acculynx-api-v2/revisions/3a9e3886e400/schema)