---
title: "Get the current bearer token info"
method: GET
path: "/token-info"
tags: ["Users"]
---

# Get the current bearer token info

`GET /token-info`

Decode the bearer token used to make this request and return
its standard JWT claims (`aud`, `jti`, `iat`, `nbf`, `exp`,
`sub`). Useful as an introspection endpoint when a client
needs to know when its token expires or which user the token
is currently bound to without parsing the JWT itself.

The token is verified with Trybe's signing key before the
claims are returned, so a successful response also confirms
the token is currently valid. The response only includes the
six claims listed above; custom claims and private extensions
are intentionally stripped.

## Response `200`

The decoded JWT claims for the caller's bearer token.

- TokenInfo — Standard JWT claims decoded from the caller's bearer token. All timestamps are seconds since the Unix epoch (i.e. standard JWT NumericDate). Custom or private claims are not included.
  - `aud` string — The audience claim — the OAuth client ID the token was issued to.
  - `jti` string — Unique identifier for this specific token, mirroring the record in Trybe's access-token store.
  - `iat` integer — Issued-at timestamp, in seconds since the Unix epoch.
  - `nbf` integer — Not-before timestamp, in seconds since the Unix epoch. The token is not valid before this instant.
  - `exp` integer — Expiry timestamp, in seconds since the Unix epoch. The token cannot be used to authenticate after this instant.
  - `sub` string — Subject — the ID of the user (or API user) the token is bound to.

## Other responses

- `401` — The user is unauthenticated

---

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