List Tokens
const url = 'https://example.com/iam/v1/tokens';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/iam/v1/tokensReturns a paginated list of the authenticated user’s active session tokens.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”The maximum number of tokens to return. The service may return fewer than this value. If unspecified, at most 20 tokens will be returned. The maximum value is 100; values above 100 will be coerced to 100.
A page token, received from a previous ListTokens call.
Provide this to retrieve the subsequent page. When paginating,
all other parameters provided to ListTokens must match the call
that provided the page token.
AIP-160 filter expression
AIP-132 order_by expression
Responses
Section titled “ Responses ”OK
ListTokensResponse
Response message for ListTokens.
Note: This API intentionally omits total_size from list responses.
Keyset pagination does not support efficient total count computation
(COUNT(*) requires a full table scan). Per AIP-158, total_size is optional.
object
The list of tokens
Token resource — an opaque session token for an authenticated user. The raw token value is never exposed after creation; only metadata is returned.
object
SHA-512 hex fingerprint of the raw token (128 lowercase hex chars). Acts as both the natural identifier and the lookup key — clients pass this back to RevokeToken / Get / List operations.
Session context captured at token creation time
object
The client IP address at the time the token was created
The User-Agent header value at the time the token was created
Expiration Timestamp
The timestamp when the token expires and can no longer be used for authentication
Created Timestamp
The timestamp when the token was created
A token, which can be sent as page_token to retrieve the next page.
If this field is empty, there are no subsequent pages.
Example generated
{ "tokens": [ {} ], "next_page_token": "example"}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}