---
title: "List managed access tokens"
method: GET
path: "/v4/tokens/managed"
tags: ["Authentication"]
---

# List managed access tokens

`GET /v4/tokens/managed`

Returns all managed API access tokens for the client.

## Response `200`

Successful response

- ManagedAccessTokenResponse[]
  - `access_token` string, required
  - `access_token_id` string, required
  - `access_token_response` AccessTokenResponse, required — Access-token metadata returned by `POST /v4/tokens`, `POST /v4/tokens/openid-connect/authorization-code-flow`, `GET /v4/tokens`, `GET /v4/tokens/{token}`, and `PUT /v4/tokens/exchange/{token}`. Pass `access_token` in the `Authorization` header (`Bearer ...`) on subsequent requests.
    - `access_token` string — Token string. Send as `Authorization: Bearer <access_token>` on subsequent requests, or as the `access_token` query parameter / `extole_token` cookie.
    - `client_id` string — Stable Extole identifier for the client (tenant) this token authenticates against.
    - `expires_in` integer — Seconds until this token expires. Once expired, requests using it return `401 invalid_access_token`; rotate via `PUT /v4/tokens/exchange/{token}` before expiry to keep long-lived integrations alive.
    - `identity_id` string — Stable Extole identifier for the identity (user, managed identity, or resource) that this token represents.
    - `person_id` string — Deprecated alias for `identity_id`. New integrations should use `identity_id`.
    - `scopes` string[] — Authorization scopes granted to this token. Determines which API operations the token may invoke.
    - `type` 'MANAGED' | 'RESOURCE' | 'USER' — Authentication shape backing the token. `USER` represents a human dashboard user, `MANAGED` an OAuth-style managed identity, and `RESOURCE` a scoped per-resource token.
  - `client_id` string, required
  - `create_date` string, required — [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) or [RFC 9557](https://datatracker.ietf.org/doc/html/rfc9557#section-4) date-time with a numeric [UTC offset](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and an optional [IANA time-zone](https://datatracker.ietf.org/doc/html/rfc9557#section-4) suffix in square brackets. Precision up to milliseconds.
  - `created_at` integer, required
  - `expire_date` string, required — [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) or [RFC 9557](https://datatracker.ietf.org/doc/html/rfc9557#section-4) date-time with a numeric [UTC offset](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and an optional [IANA time-zone](https://datatracker.ietf.org/doc/html/rfc9557#section-4) suffix in square brackets. Precision up to milliseconds.
  - `expires_in` integer, required
  - `name` string, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `402` — Payment Required
- `403` — Forbidden
- `415` — Unsupported Media Type
- `429` — Too Many Requests

---

[API](https://skmtc.net/extole/apis/integration-api-server-to-extole.md) · [All operations](https://skmtc.net/extole/apis/integration-api-server-to-extole/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/extole/integration-api-server-to-extole/revisions/c16e62e66755/schema)