RevnuDocs
Browse the Docs▾

API Reference / Get the current token

Get the current token

GET/api/v1/me

Who this token is: label, scopes, the account it belongs to, and the rate limits it is held to. Needs no scope.

Last updated

Needs no scope, so it is the call to verify any token with.

curl -H "Authorization: Bearer $REVNU_API_TOKEN" https://revnu.com/api/v1/me

Response

{
  "me": {
    "tokenId": "…",
    "label": "wall dashboard",
    "scopes": ["review:read", "review:write"],
    "createdAt": 1789837627802,
    "lastUsedAt": 1789851456304,
    "account": { "id": "…", "name": "Acme" },
    "limits": {
      "reads": { "perMinute": 300, "burst": 600 },
      "writes": { "perMinute": 60, "burst": 120 },
      "messages": { "perMinute": 30, "burst": 60 },
      "account": { "perMinute": 900, "burst": 1800 }
    }
  }
}

401 for an unknown or revoked token.

Agents: this page is also markdown at /docs/me.md, answers Accept: text/markdown, and is listed in /docs/llms.txt.

Frequently Asked Questions

None. Any live token can call it, which is what makes it the verification call. Every other route names the scope it needs, and a token without that scope gets `403` with `requiredScope` in the body.