- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- IAM Permissions
Returns list of target sites with its domain verification status. This method can only be called under data store with BASIC_SITE_SEARCH state at the moment.
HTTP request
GET https://discoveryengine.googleapis.com/v1/{siteSearchEngine=projects/*/locations/*/collections/*/dataStores/*/siteSearchEngine}:fetchDomainVerificationStatus
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| siteSearchEngine | 
 Required. The site search engine resource under which we fetch all the domain verification status.  | 
Query parameters
| Parameters | |
|---|---|
| pageSize | 
 Requested page size. Server may return fewer items than requested. If unspecified, server will pick an appropriate default. The maximum value is 1000; values above 1000 will be coerced to 1000. If this field is negative, an INVALID_ARGUMENT error is returned. | 
| pageToken | 
 A page token, received from a previous  When paginating, all other parameters provided to  | 
Request body
The request body must be empty.
Response body
Response message for SiteSearchEngineService.FetchDomainVerificationStatus method.
If successful, the response body contains data with the following structure:
| JSON representation | 
|---|
| {
  "targetSites": [
    {
      object ( | 
| Fields | |
|---|---|
| targetSites[] | 
 List of TargetSites containing the site verification status. | 
| nextPageToken | 
 A token that can be sent as  | 
| totalSize | 
 The total number of items matching the request. This will always be populated in the response. | 
Authorization scopes
Requires one of the following OAuth scopes:
- https://www.googleapis.com/auth/cloud-platform
- https://www.googleapis.com/auth/discoveryengine.readwrite
For more information, see the Authentication Overview.
IAM Permissions
Requires the following IAM permission on the siteSearchEngine resource:
- discoveryengine.siteSearchEngines.fetchDomainVerificationStatus
For more information, see the IAM documentation.