Re-identifies content that has been de-identified. See https://cloud.google.com/sensitive-data-protection/docs/pseudonymization#re-identification_in_free_text_code_example to learn more.
HTTP request
The URLs use gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
parent |
Required. Parent resource name. The format of this value varies depending on whether you have specified a processing location:
The following example
Authorization requires the following IAM permission on the specified resource
|
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "reidentifyConfig": { object ( |
Fields | |
---|---|
reidentifyConfig |
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:
|
inspectConfig |
Configuration for the inspector. |
item |
The item to re-identify. Will be treated as text. |
inspectTemplateName |
Template to use. Any configuration directly specified in |
reidentifyTemplateName |
Template to use. References an instance of |
locationId |
Deprecated. This field has no effect. |
Response body
If successful, the response body contains an instance of ReidentifyContentResponse
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.