Method: accountstatuses.list

Page Summary

Lists the statuses of sub-accounts within a multi-client Merchant Center account.
Allows filtering by name, destination, and pagination for large result sets.
Requires authorization with the https://www.googleapis.com/auth/content scope.
Provides details on HTTP request structure, parameters, and the expected response format.
Employs a GET request to the specified endpoint with optional query parameters.

Lists the statuses of the sub-accounts in your Merchant Center account.

GET https://shoppingcontent.googleapis.com/content/v2.1/{merchantId}/accountstatuses

Parameters

Parameters
`merchantId`	`string` The ID of the managing account. This must be a multi-client account.

merchantId

string

The ID of the managing account. This must be a multi-client account.

Parameters
`maxResults`	`integer ( uint32 format)` The maximum number of account statuses to return in the response, used for paging.
`pageToken`	`string` The token returned by the previous request.
`destinations[]`	`string` If set, only issues for the specified destinations are returned, otherwise only issues for the Shopping destination.
`name`	`string` If set, only the accounts with the given name (case sensitive) will be returned.

The request body must be empty.

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

JSON representation
{ "nextPageToken" : string , "kind" : string , "resources" : [ { object ( `AccountStatus` ) } ] }

Fields

Fields
`nextPageToken`	`string` The token for the retrieval of the next page of account statuses.
`kind`	`string` Identifies what kind of resource this is. Value: the fixed string " `content#accountstatusesListResponse` ".
`resources[]`	`object ( AccountStatus )`

nextPageToken

string

The token for the retrieval of the next page of account statuses.

kind

string

Identifies what kind of resource this is. Value: the fixed string " content#accountstatusesListResponse ".

resources[]

Requires one of the following OAuth scopes:

For more information, see the OAuth 2.0 Overview .