# Get all database rulesets

Endpoint: GET /database-rulesets
Version: 5.1.42
Security: api_key

## Query parameters:

  - `environment_id` (integer)
    The ID of the environment to get all database rulesets from

  - `page_number` (integer)
    The page number for which to get database rulesets. This will default to the first page if excluded

  - `page_size` (integer)
    The maximum number of objects to return. This will default to the DefaultApiPageSize setting if not provided

## Response 200 fields (application/json):

  - `_pageInfo` (object)

  - `_pageInfo.numberOnPage` (integer)
    The number of items on this page. This should always match the page size unless it is the last page.

  - `_pageInfo.total` (integer)
    The total number of items

  - `responseList` (array)
    Example: [{"rulesetName":"Rule123","databaseConnectorId":1}]

  - `responseList.databaseRulesetId` (integer)
    The ID of the database ruleset. This field is set by the Masking Engine.

  - `responseList.rulesetName` (string, required)
    The name of the ruleset. This must be unique within an environment.
    Example: "Rule123"

  - `responseList.databaseConnectorId` (integer, required)
    The ID of the database connector that this ruleset corresponds to. Note that the ruleset will be created on the same environment as its connector.
    Example: 1

  - `responseList.refreshDropsTables` (boolean)
    This field applies to the case where a Table Metadata exists in the Masking Engine, but the corresponding table no longer exists in the external database (e.g. if the table has been deleted or renamed). In that event, True will cause the refresh operation to delete the invalid Table Metadata, whereas False will fail the refresh instead.


## Response 400 fields

## Response 403 fields

## Response 404 fields