---
title: "List tokens"
method: GET
path: "/api/v1/tokens"
tags: ["Cloud"]
---

# List tokens

`GET /api/v1/tokens`

List tokens.

## Response `200`

The request has succeeded.

- Token[]
  - `createdAt` string, date-time, required — The date and time the token was created.
  - `createdBy` string, required — The user that created the token.
  - `expiresAt` string, date-time, nullable — The date and time the token expires.
  - `id` string, required — Readonly unique ULID identifier.
  - `name` string, required — The name of the token.
  - `permissions` TokenPermission[], required — The permissions of the token.
  - `role` 'org:openmeter_read_only' | 'org:openmeter_read_write' — The assigned role of the token.
  - `token` string, required — The token secret. Full secret is only visible when creating a new token. When listing tokens, the secret is redacted to the last 5 characters.

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `403` — The server understood the request but refuses to authorize it.
- `412` — One or more conditions given in the request header fields evaluated to false when tested on the server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `503` — The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.
- `default` — An unexpected error response.

---

[API](https://skmtc.dev/openmeter/apis/openmeter-cloud-api.md) · [All operations](https://skmtc.dev/openmeter/apis/openmeter-cloud-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/openmeter/openmeter-cloud-api/revisions/c9c0ec9cffe9/schema)