---
title: "View Alert Report"
method: POST
path: "/msp/reporting/v1/reports/mspEPAlert"
tags: ["Endpoints Reports"]
---

# View Alert Report

`POST /msp/reporting/v1/reports/mspEPAlert`

This report provides details about all alerts generated for MSP customers. Specify the status of the alert to narrow down the data in your report. This filter parameter can have one of the following values: 

 **Yes:** To retrieve data for active alerts only. It lists the currently triggered alerts that require your attention. 

 **No:** To retrieve data for resolved or deleted alerts only. 

This API may be updated without any prior notification. Check the API documentation for the latest updates regularly.

## Headers

- `Authorization` string, required

## Request body

- object
  - `filters` object
    - `pageSize` integer — Specify the maximum number of records that should returned in a response. Maximum limit is 500 records. Default pageSize is 100.
    - `filterBy` object[] — Select the filters to be applied to the report.
      - `fieldName` 'customerGlobalId' | 'accountName' | 'customerName' | 'entity' | 'alertDetails' | 'firstOccurrence' | 'lastOccurrence' | 'active' | 'severity' — Specify the name of the filter.
      - `operator` 'EQUAL' | 'GT' | 'GTE' | 'LT' | 'LTE' | 'CONTAINS' | 'NOTEQUAL' — The operators that are supported for the filter are - EQUAL, NOTEQUAL, CONTAINS, LT (less-than), LTEQ (less-than-or-equal), GT (greater-than), GTEQ (greater-than-or-equal).
      - `value` union — Specify the value of the filter applied to the report.
        - string — string
        - integer — integer
        - string[] — array of strings
        - integer[] — array of integers
  - `pageToken` string — Specify the token to access the results on the next page. Keep this field blank for the first request. To view the results on the next page, use the value received in the 'nextPageToken' parameter of the previous response.

## Response `200`

Success

- GetAlertReportDataResponse
  - `data` AlertReportData[]
    - `customerGlobalId` string — Unique ID of the customer.
    - `accountName` string — Account name defined for the customer
    - `customerName` string — Customer name defined for the customer
    - `entity` string — The username and device of the user.
    - `alertDetails` string — The details about the alert generated.
    - `firstOccurrence` string, date-time — The date and time when the alert was generated for the first time. The time is in the UTC time zone. Example - 2019-10-25T00:00:00Z
    - `lastOccurrence` string, date-time — The date and time when the alert was generated for the last time. The time is in the UTC time zone. Example - 2019-10-25T00:00:00Z
    - `active` string — Displays information whether the alert generated is active or not.
    - `severity` string — Displays the severity type of the alert. Example:- critical, high, warning.
  - `lastSyncTimestamp` string, date-time — The time stamp until which the report data was returned. The time is in the UTC time zone.
  - `filters` object — Filters applied on the report.
  - `nextPageToken` string — The token to access the next page of results. This parameter will be empty for the last page of the results. This token is valid for 5 minutes.

## Other responses

- `400` — Bad Request
- `404` — The requested resource was not found.
- `500` — The request was not processed due to an internal error.

---

[API](https://skmtc.net/druva/apis/authentication.md) · [All operations](https://skmtc.net/druva/apis/authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/druva/authentication/versions/2af2bf148b25/schema)