Google Business Performance API has a NEW API method that allows fetching multiple `DailyMetrics` in a single API request.
Review the deprecation schedule and instructions to migrate over from v4 reportInsights API method to Google Business Profile Performance API.

Method: accounts.locations.list

Lists the locations for the specified account.

HTTP request


The URL uses gRPC Transcoding syntax.

Path parameters



The name of the account to fetch locations from. If the Account is of AccountType PERSONAL, only Locations that are directly owned by the Account are returned, otherwise it will return all accessible locations from the Account, either directly or indirectly.

Query parameters



How many locations to fetch per page. Default is 100, minimum is 1, and maximum page size is 100.



If specified, it fetches the next page of locations. The page token is returned by previous calls to locations.list when there were more locations than could fit in the requested page size.



A filter constraining the locations to return. The response includes only entries that match the filter. If filter is empty, then constraints are applied and all locations (paginated) are retrieved for the requested account.

For more information about valid fields and example usage, see Work with Location Data Guide.



The BCP 47 code of language to get display location properties in. If this language is not available, they will be provided in the language of the location. If neither is available, they will be provided in English.

Deprecated. After August 15th, 2020, this field will no longer be applied. Instead, the language of the location will always be used.



Sorting order for the request. Multiple fields should be comma-separated, following SQL syntax. The default sorting order is ascending. To specify descending order, a suffix " desc" should be added. Valid fields to orderBy are locationName and storeCode. For example: "locationName, storeCode desc" or "locationName" or "storeCode desc"

Request body

The request body must be empty.

Response body

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

Response message for Locations.ListLocations.

JSON representation
  "locations": [
      object (Location)
  "nextPageToken": string,
  "totalSize": integer

object (Location)

The locations.



If the number of locations exceeded the requested page size, this field is populated with a token to fetch the next page of locations on a subsequent call to locations.list. If there are no more locations, this field is not present in the response.



The approximate number of Locations in the list irrespective of pagination.

Authorization Scopes

Requires one of the following OAuth scopes:


For more information, see the OAuth 2.0 Overview.