# Get the current token

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

Canonical: https://revnu.com/docs/me

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

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

## Response

```json
{
  "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.

## Frequently asked questions

### Which scope does this need?

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.

### Are responses cached?

No. Every response is `Cache-Control: no-store`, so what you read is current.