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 Identity and Access Management
  • Secure use of Yandex Cloud
  • Access management
  • Pricing policy
  • Role reference
  • Terraform reference
    • Authentication with the API
      • Overview
        • Overview
        • List
        • Revoke
  • Monitoring metrics
  • Audit Trails events
  • Release notes

In this article:

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

Identity and Access Management API, REST: RefreshToken.List

Written by
Yandex Cloud
Updated at November 26, 2024
  • HTTP request
  • Query parameters
  • Response
  • RefreshToken

List subjects Refresh Tokens.

HTTP requestHTTP request

GET https://iam.api.cloud.yandex.net/iam/v1/refreshTokens

Query parametersQuery parameters

Field

Description

subjectId

string

pageSize

string (int64)

The maximum number of results per page to return. If the number of available
results is larger than pageSize,
the service returns a ListRefreshTokensResponse.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 pageToken
to the ListRefreshTokensResponse.nextPageToken
returned by a previous list request.

filter

string

A filter expression that filters refresh tokens listed in the response.

The expression must specify:

  1. The field name. Currently you can use filtering only on RefreshToken.clientInstanceInfo, RefreshToken.clientId or RefreshToken.protectionLevel fields.
  2. The operator. An = operator can be used for all fields. An 'IN' operator can be used for RefreshToken.protectionLevel.
  3. The value. The value must be in double quotes ("). Must be 3-63 characters long and match the regular expression [a-zA-Z][_-a-zA-Z0-9]{1,61}[a-z0-9].
    Example of a filter: client_instance_info="clientInstanceInfo" AND protection_level IN ("INSECURE_KEY_DPOP", "SECURE_KEY_DPOP").

ResponseResponse

HTTP Code: 200 - OK

{
  "refreshTokens": [
    {
      "id": "string",
      "clientInstanceInfo": "string",
      "clientId": "string",
      "subjectId": "string",
      "createdAt": "string",
      "expiresAt": "string",
      "lastUsedAt": "string",
      "protectionLevel": "string"
    }
  ],
  "nextPageToken": "string"
}

Field

Description

refreshTokens[]

RefreshToken

List of Refresh Tokens

nextPageToken

string

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

RefreshTokenRefreshToken

Field

Description

id

string

Refresh Token id.

clientInstanceInfo

string

Information about the app for which the Refresh Token was issued.

clientId

string

The OAuth client identifier for which the Refresh Token was issued.

subjectId

string

The subject identifier for whom the Refresh Token was issued.

createdAt

string (date-time)

Refresh token creation time.

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).

expiresAt

string (date-time)

Refresh token expiration time.

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).

lastUsedAt

string (date-time)

Timestamp for the last authentication using this Refresh Token.

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).

protectionLevel

enum (ProtectionLevel)

Protection level of the refresh token.

It shows whether DPOP was used to protect the Refresh Token and and the level of security of the storage used for the DPOP key.

  • PROTECTION_LEVEL_UNSPECIFIED
  • NO_PROTECTION: Refresh token without DPOP
  • INSECURE_KEY_DPOP: Refresh token with dpop. The dpop key is not a YubiKey PIV key with required pin/touch policy and attestation.
  • SECURE_KEY_DPOP: Refresh token with dpop. The dpop key is a YubiKey PIV key with required pin/touch policy and attestation.

Was the article helpful?

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