Method: projects.locations.content.inspect

Finds potentially sensitive info in content. This method has limits on input size, processing time, and output size.

When no InfoTypes or CustomInfoTypes are specified in this request, the system will automatically choose what detectors to run. By default this may be all types, but may change over time as detectors are updated.

For how to guides, see and,

HTTP request


The URL uses gRPC Transcoding syntax.

Path parameters



Parent resource name.

The format of this value varies depending on whether you have specified a processing location:

  • Projects scope, location specified: projects/PROJECT_ID/locations/LOCATION_ID
  • Projects scope, no location specified (defaults to global): projects/PROJECT_ID

The following example parent string specifies a parent project with the identifier example-project, and specifies the europe-west3 location for processing data:


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


Request body

The request body contains data with the following structure:

JSON representation
  "inspectConfig": {
    object (InspectConfig)
  "item": {
    object (ContentItem)
  "inspectTemplateName": string,
  "locationId": string

object (InspectConfig)

Configuration for the inspector. What specified here will override the template referenced by the inspectTemplateName argument.


object (ContentItem)

The item to inspect.



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.



Deprecated. This field has no effect.

Response body

If successful, the response body contains an instance of InspectContentResponse.

Authorization scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.