# List Portfolio Event Rules

Get all notification  for the given . Notification event rules allow you to control which events you wish to monitor for the  contained within the given .

Endpoint: GET /monitoring/portfolios/{portfolioId}/eventRules
Version: 1.10.9
Security: bearerToken

## Path parameters:

  - `portfolioId` (number, required)
    The unique identifier for the portfolio that you wish to retrieve notification event rules for, obtained from .

## Response 200 fields (application/json):

  - `isActive` (boolean)
    Shows whether the notification event rule has been enabled for the given portfolio.

  - `ruleCode` (number)
    The unique identifier for the notification event rule.
    Example: 101

  - `ruleCountryCode` (string)
    The ISO/Alpha 2 format country code for the notification event rule. "XX" is used for global rules that apply to companies from all countries.
    Example: "XX"

  - `ruleType` (number)
    The unique identifier of the  for the notification event rule.
    Example: 4

  - `ruleTypeName` (string)
    A short description of the  for the notification event rule.
    Example: "Rating band change - 3 input"

  - `name` (string)
    The name for the notification event rule.
    Example: "International Rating | Reduce by {0} Band(s) OR Less than Band {1}"

  - `param0` (string)
    Some notification event rules may include input parameters used to tailor the notifications generated to your preference.
    Example: "1"

  - `param1` (string)
    Some notification event rules may include input parameters used to tailor the notifications generated to your preference.
    Example: "A"

  - `param2` (string)
    Some notification event rules may include input parameters used to tailor the notifications generated to your preference.
    Example: "A"

## Response 400 fields (application/json):

  - `correlationId` (string)
    A unique ID assigned to this request.

  - `message` (string)

  - `details` (string)
    Provides further information on why the request was rejected

## Response 401 fields (application/json):

  - `error` (string)

## Response 403 fields (application/json):

  - `message` (string)
    Example: "Access forbidden"

## Response 404 fields (application/json):

  - `correlationId` (string)
    A unique ID assigned to this request.

  - `message` (string)

  - `details` (string)
    Provides further information on why the request was rejected