PUT /v1/dataMaskingRules/{id}

Update an existing data masking rule. All properties specified in the request are replaced. Missing properties are set to their default values. The rule name is immutable and cannot be changed after creation.

Servers

Path parameters

Name Type Required Description
id String Yes

Identifier of the data masking rule to update.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
description String No

Optional description of the data masking rule. Provide context about what PII this rule masks and why it's needed.

enabled Boolean Yes

Whether the data masking rule is active. Only enabled rules are applied to search results. Set to false to temporarily disable a rule without deleting it.

Default value: true

maskString String No

The string to replace matched PII with. Defaults to '##redactedPII##' if not specified. Use descriptive mask strings like 'EMAIL_REDACTED' or 'PHONE_REDACTED' for clarity.

Default value: "##redactedPII##"

regexPattern String Yes

Regular expression pattern to match PII data that should be masked. The pattern must be valid according to Java regex syntax. All matches in search results will be replaced with the mask string.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.