Container Registry API, REST: Repository.list

Retrieves the list of Repository resources in the specified registry.

HTTP request

GET https://container-registry.api.il.nebius.cloud/container-registry/v1/repositories

Parameter	Description
registryId	ID of the registry to list repositories in. To get the registry ID use a list request. The maximum string length in characters is 50.
folderId	ID of the folder to list registries in. folderId is ignored if a registryId is specified in the request. To get the folder ID use a list request. The maximum string length in characters is 50.
pageSize	The maximum number of results per page to return. If the number of available results is larger than pageSize, the service returns a nextPageToken that can be used to get the next page of results in subsequent list requests. Default value: 100. The maximum value is 1000.
pageToken	Page token. To get the next page of results, set pageToken to the nextPageToken returned by a previous list request. The maximum string length in characters is 100.
filter	A filter expression that filters resources listed in the response. The expression must specify: The field name. Currently you can use filtering only on Repository.name field. An `=` operator. The value in double quotes (`"`). Must be 3-63 characters long and match the regular expression `[a-z][-a-z0-9]{1,61}[a-z0-9]`. The maximum string length in characters is 1000.
orderBy	The maximum string length in characters is 100.

HTTP Code: 200 - OK

{
  "repositories": [
    {
      "name": "string",
      "id": "string"
    }
  ],
  "nextPageToken": "string"
}

Field	Description
repositories[]	object List of Repository resources.
repositories[]. name	string Name of the repository. The name is unique within the registry.
repositories[]. id	string Output only. ID of the repository.
nextPageToken	string This token allows you to get the next page of results for list requests. If the number of results is larger than pageSize, use the nextPageToken as the value for the pageToken query parameter in the next list request. Each subsequent list request will have its own nextPageToken to continue paging through the results.