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
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Billing
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
    • Authentication with the API
      • Overview
        • Overview
        • Get
        • List
  • Audit Trails events

In this article:

  • gRPC request
  • ListServicesRequest
  • ListServicesResponse
  • Service
  1. API reference
  2. gRPC
  3. Service
  4. List

Billing API, gRPC: ServiceService.List

Written by
Yandex Cloud
Updated at November 26, 2024
  • gRPC request
  • ListServicesRequest
  • ListServicesResponse
  • Service

Retrieves the list of services.

gRPC requestgRPC request

rpc List (ListServicesRequest) returns (ListServicesResponse)

ListServicesRequestListServicesRequest

{
  "filter": "string",
  "page_size": "int64",
  "page_token": "string"
}

Field

Description

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 the yandex.cloud.billing.v1.Service.id 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].

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 ListServicesResponse.next_page_token
that can be used to get the next page of results in subsequent list requests.

page_token

string

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

ListServicesResponseListServicesResponse

{
  "services": [
    {
      "id": "string",
      "name": "string",
      "description": "string"
    }
  ],
  "next_page_token": "string"
}

Field

Description

services[]

Service

List of services.

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 ListServicesRequest.page_size, use
next_page_token as the value
for the ListServicesRequest.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.

ServiceService

A Service resource.

Field

Description

id

string

ID of the service.

name

string

Name of the service, e.g. Compute Cloud, VPC.

description

string

Description of the service.

Was the article helpful?

Previous
Get
Next
Overview
© 2025 Direct Cursus Technology L.L.C.