# Get information about specific alert from all triggered alerts for the account POST /v3/account-triggered-alerts/alerts/{alertId} Endpoint: POST /v3/account-triggered-alerts/alerts/{alertId} Security: API_Key ## Path parameters: - `alertId` (integer, required) ## Query parameters: - `page` (integer) Number of results page of an endpoint with paginated results - `size` (integer) - `sortBy` (string) Enum: "RUN_DATE", "DATA_SOURCE_NAME", "PAGES_WITH_TRIGGERED_ALERTS" - `sortDesc` (boolean) Controls sorting order ## Request fields (application/json): - `runDateRange` (object) Should have and/or dates defined. is inclusive and is exclusive. date should be after date. - `runDateRange.from` (string) Date-time in [RFC3339 profile ISO 8601 format](https://www.ietf.org/rfc/rfc3339.txt) with the following additional restrictions: 1. An uppercase T must separate the date and time portions. 2. An uppercase Z must denote that a numeric time zone offset isn't present. In general, these timestamp requirements are the same in [AWS Step Functions - Choice Rules](https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-choice-state.html) Example: "2016-08-18T17:33:00Z" - `runDateRange.to` (string) Date-time in [RFC3339 profile ISO 8601 format](https://www.ietf.org/rfc/rfc3339.txt) with the following additional restrictions: 1. An uppercase T must separate the date and time portions. 2. An uppercase Z must denote that a numeric time zone offset isn't present. In general, these timestamp requirements are the same in [AWS Step Functions - Choice Rules](https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-choice-state.html) Example: "2016-08-18T17:33:00Z" - `itemName` (string) optional "item name contains substring" filter - `itemLabels` (array) non-empty array of labels present on an item, works as "item has all specified labels" filter - `itemType` (string) Enum: "AUDIT", "WEB_JOURNEY" - `folders` (array) non-empty array of folders with domains (subfolders), items from which will be included in response - `folders.folderId` (integer, required) ID of a folder Example: 123 - `folders.domains` (array) null or empty array of domains (subfolders) present on an item, works as "null or empty if entire folder (all domains in a folder), otherwise specific domain IDs" Example: [123] ## Response 200 fields (application/json): - `metadata` (object, required) Common metadata for iterable - `metadata.pagination` (object, required) - `metadata.pagination.totalCount` (integer, required) Total number of items available from all result pages combined - `metadata.pagination.totalPageCount` (integer, required) Total number of pages available - `metadata.pagination.pageSize` (integer, required) Page size - number of items per result page configured by query parameter or default page size - `metadata.pagination.currentPageSize` (integer, required) Number of items in current result page - `metadata.pagination.currentPageNumber` (integer, required) Current page number/ordinal - `dataSources` (array, required) - `dataSources.status` (string, required) All statuses except and mean that alert/metric could not be computed. Statuses: - UNKNOWN_ERROR: data retrieval or alert computation failed - RUN_NOT_FOUND: requested run not found - NO_VALUE: no data found for requested run (e.g. rules or consent categories were not applied) - PREVIOUS_RUN_NOT_FOUND: previous run not found for run-over-run metric change alert - PREVIOUS_RUN_NO_VALUE: no data found for previous run for run-over-run metric change alert Enum: "TRIGGERED", "NOT_TRIGGERED", "UNKNOWN_ERROR", "RUN_NOT_FOUND", "NO_VALUE", "PREVIOUS_RUN_NOT_FOUND", "PREVIOUS_RUN_NO_VALUE" - `dataSources.actualValue` (number) Value of the computed metric or its change. - `dataSources.currentRunValue` (number) Value of computed metric for current run. Present when alert is configured on metric change, not on single run metric value - `dataSources.previousRunValue` (number) Value of computed metric for previous run. Present when alert is configured on metric change, not on single run metric value - `dataSources.appliedAlertPageCount` (integer, required) - `dataSources.triggeredAlertAffectedPageCount` (integer, required) - `dataSources.runDate` (string, required) Date-time in [RFC3339 profile ISO 8601 format](https://www.ietf.org/rfc/rfc3339.txt) with the following additional restrictions: 1. An uppercase T must separate the date and time portions. 2. An uppercase Z must denote that a numeric time zone offset isn't present. In general, these timestamp requirements are the same in [AWS Step Functions - Choice Rules](https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-choice-state.html) Example: "2016-08-18T17:33:00Z" - `dataSources.itemName` (string, required) - `dataSources.itemType` (string, required) Enum: "AUDIT", "WEB_JOURNEY" - `dataSources.runId` (integer, required) Example: 33010 - `dataSources.itemId` (integer, required) ID of the item that can have assigned Alert(s) onto it. See also ## Response 400 fields (application/json): - `timestamp` (string) - `message` (string) - `details` (string) - `validationReport` (object) ## Response 401 fields (application/json): - `timestamp` (string) - `message` (string) - `details` (string) - `validationReport` (object) ## Response 404 fields (application/json): - `timestamp` (string) - `message` (string) - `details` (string) - `validationReport` (object)