Method: projects.content.reidentify

• HTTP request
• Path parameters
• Request body
  • JSON representation
• Response body
• Authorization scopes
• Try it!

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

Choose a location:

global africa-south1 asia-east1 asia-east2 asia-northeast1 asia-northeast2 asia-northeast3 asia-south1 asia-south2 asia-southeast1 asia-southeast2 australia-southeast1 australia-southeast2 europe-central2 europe-north1 europe-north2 europe-southwest1 europe-west1 europe-west10 europe-west12 europe-west2 europe-west3 europe-west4 europe-west6 europe-west8 europe-west9 me-central1 me-central2 me-west1 northamerica-northeast1 northamerica-northeast2 northamerica-south1 southamerica-east1 southamerica-west1 us-central1 us-east1 us-east4 us-east5 us-south1 us-west1 us-west2 us-west3 us-west4 us-west8

The URLs use gRPC Transcoding syntax.

Path parameters

Parameters

parent

string Required. Parent resource name. The format of this value varies depending on whether you have specified a processing location: Projects scope, location specified: projects/{projectId}/locations/{locationId} Projects scope, no location specified (defaults to global): projects/{projectId} The following example parent string specifies a parent project with the identifier example-project, and specifies the europe-west3 location for processing data: parent=projects/example-project/locations/europe-west3 Authorization requires the following 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, "locationId": 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: CryptoDeterministicConfig CryptoReplaceFfxFpeConfig
inspectConfig	object (InspectConfig) Configuration for the inspector.
item	object (ContentItem) The item to re-identify. Will be treated as text.
inspectTemplateName	string 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 Template to use. References an instance of DeidentifyTemplate. Any configuration directly specified in reidentifyConfig or inspectConfig will override those set in the template. The DeidentifyTemplate used must include only reversible transformations. 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.
locationId	string 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.