Method: projects.content.reidentify

Re-identifies content that has been de-identified. See https://cloud.google.com/dlp/docs/pseudonymization#re-identification_in_free_text_code_example to learn more.

HTTP request

POST https://dlp.googleapis.com/v2/{parent=projects/*}/content:reidentify

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
parent

string

The parent resource name.

Authorization requires the following Google IAM permission on the specified resource parent:

  • serviceusage.services.use

Request body

The request body contains data with the following structure:

JSON representation
{
  "reidentifyConfig": {
    object(DeidentifyConfig)
  },
  "inspectConfig": {
    object(InspectConfig)
  },
  "item": {
    object(ContentItem)
  },
  "inspectTemplateName": string,
  "reidentifyTemplateName": string
}
Fields
reidentifyConfig

object(DeidentifyConfig)

Configuration for the re-identification of the content item. This field shares the same proto message type that is used for de-identification, however its usage here is for the reversal of the previous de-identification. Re-identification is performed by examining the transformations used to de-identify the items and executing the reverse. This requires that only reversible transformations be provided here. The reversible transformations are:

  • CryptoReplaceFfxFpeConfig

inspectConfig

object(InspectConfig)

Configuration for the inspector.

item

object(ContentItem)

The item to re-identify. Will be treated as text.

inspectTemplateName

string

Optional template to use. Any configuration directly specified in inspectConfig will override those set in the template. Singular fields that are set in this request will replace their corresponding fields in the template. Repeated fields are appended. Singular sub-messages and groups are recursively merged.

reidentifyTemplateName

string

Optional template to use. References an instance of DeidentifyTemplate. Any configuration directly specified in reidentifyConfig or inspectConfig will override those set in the template. Singular fields that are set in this request will replace their corresponding fields in the template. Repeated fields are appended. Singular sub-messages and groups are recursively merged.

Response body

If successful, the response body contains data with the following structure:

Results of re-identifying a item.

JSON representation
{
  "item": {
    object(ContentItem)
  },
  "overview": {
    object(TransformationOverview)
  }
}
Fields
item

object(ContentItem)

The re-identified item.

overview

object(TransformationOverview)

An overview of the changes that were made to the item.

Authorization Scopes

Requires the following OAuth scope:

  • https://www.googleapis.com/auth/cloud-platform

For more information, see the Authentication Overview.

Try it!

Was this page helpful? Let us know how we did:

Send feedback about...

Cloud Data Loss Prevention