# Copy database ruleset by ID

Endpoint: PUT /database-rulesets/{databaseRulesetId}/copy
Version: 5.1.42
Security: api_key

## Path parameters:

  - `databaseRulesetId` (integer, required)
    The ID of the database ruleset to copy

## Request fields (application/json):

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

## Response 200 fields (application/json):

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

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

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

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