Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Load Testing
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
    • API authentication
      • Overview
        • Overview
        • Create
        • Get
        • List
        • Delete
  • Audit Trails events
  • Release notes

In this article:

  • HTTP request
  • Query parameters
  • Response
  • Config
  1. API reference
  2. REST
  3. Config
  4. List

Load Testing API, REST: Config.List

Written by
Yandex Cloud
Updated at October 3, 2025
  • HTTP request
  • Query parameters
  • Response
  • Config

Retrieves the list of configs in the specified folder.

HTTP requestHTTP request

GET https://loadtesting.api.cloud.yandex.net/loadtesting/api/v1/configs

Query parametersQuery parameters

Field

Description

folderId

string

ID of the folder to list configs in.

pageSize

string (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 ListConfigsResponse.nextPageToken
that can be used to get the next page of results in subsequent list requests.
Default value: 100.

pageToken

string

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

filter

string

A filter expression that filters tests listed in the response.

ResponseResponse

HTTP Code: 200 - OK

{
  "configs": [
    {
      "id": "string",
      "folderId": "string",
      "yamlString": "string",
      "name": "string",
      "createdAt": "string",
      "createdBy": "string"
    }
  ],
  "nextPageToken": "string"
}

Field

Description

configs[]

Config

List of configs in the specified folder.

nextPageToken

string

Token for getting the next page of the list. If the number of results is greater than
the specified ListConfigsRequest.pageSize, use next_page_token as the value
for the ListConfigsRequest.pageToken parameter in the next list request.

Each subsequent page will have its own next_page_token to continue paging through the results.

ConfigConfig

Test config.

Field

Description

id

string

ID of the test config. Generated at creation time.

folderId

string

ID of the folder that the config belongs to.

yamlString

string

Config content in YAML format.

name

string

Name of the config.

createdAt

string (date-time)

Creation timestamp.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

createdBy

string

UA or SA that created the config.

Was the article helpful?

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