Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Container Registry
  • Getting started
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
    • Authentication with the API
      • Overview
        • Overview
        • Get
        • GetByName
        • List
        • ListAccessBindings
        • Upsert
        • Delete
        • SetAccessBindings
        • UpdateAccessBindings
  • Monitoring metrics
  • Audit Trails events
  • Troubleshooting
  • FAQ

In this article:

  • gRPC request
  • ListRepositoriesRequest
  • ListRepositoriesResponse
  • Repository
  1. API reference
  2. gRPC
  3. Repository
  4. List

Container Registry API, gRPC: RepositoryService.List

Written by
Yandex Cloud
Updated at November 26, 2024
  • gRPC request
  • ListRepositoriesRequest
  • ListRepositoriesResponse
  • Repository

Retrieves the list of Repository resources in the specified registry.

gRPC requestgRPC request

rpc List (ListRepositoriesRequest) returns (ListRepositoriesResponse)

ListRepositoriesRequestListRepositoriesRequest

{
  "registry_id": "string",
  "folder_id": "string",
  "page_size": "int64",
  "page_token": "string",
  "filter": "string",
  "order_by": "string"
}

Field

Description

registry_id

string

ID of the registry to list repositories in.

To get the registry ID use a RegistryService.List request.

folder_id

string

ID of the folder to list registries in.

folder_id is ignored if a ListImagesRequest.registry_id is specified in the request.

To get the folder ID use a yandex.cloud.resourcemanager.v1.FolderService.List request.

page_size

int64

The maximum number of results per page to return. If the number of available
results is larger than page_size,
the service returns a ListRepositoriesResponse.next_page_token
that can be used to get the next page of results in subsequent list requests.
Default value: 100.

page_token

string

Page token. To get the next page of results, set page_token to the
ListRepositoriesResponse.next_page_token returned by a previous list request.

filter

string

A filter expression that filters resources listed in the response.
The expression must specify:

  1. The field name. Currently you can use filtering only on Repository.name field.
  2. An = operator.
  3. 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].

order_by

string

ListRepositoriesResponseListRepositoriesResponse

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

Field

Description

repositories[]

Repository

List of Repository resources.

next_page_token

string

This token allows you to get the next page of results for list requests. If the number of results
is larger than ListRepositoriesRequest.page_size, use
the next_page_token as the value
for the ListRepositoriesRequest.page_token query parameter
in the next list request. Each subsequent list request will have its own
next_page_token to continue paging through the results.

RepositoryRepository

A Repository resource. For more information, see Repository.

Field

Description

name

string

Name of the repository.
The name is unique within the registry.

id

string

Output only. ID of the repository.

Was the article helpful?

Previous
GetByName
Next
ListAccessBindings
Yandex project
© 2025 Yandex.Cloud LLC