# List Portfolio Event Rules By Country

Endpoint to that lists all the eventRules, their status and parameters based on a portfolio Id, filtered by country. Newly created portfolios are without any notification event rules by default, but you can switch rules on/off per country or on a global basis. There are different rules available for each country due to the different type of change event data that's available. The following GET request lists all the available rules for a portfolio.

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

## Path parameters:

  - `portfolioId` (number, required)
    The unique identifier of the portfolio, obtained from .

  - `countryCode` (string, required)
    Country code to show events for.  Please note that there is one exception in that  is the only 3-character that can be accepted here.

## 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