# Check an API key

`GET /v1/me`

Any valid key, whatever its scopes: the workspace it acts in and the key itself. Use it as a connection test; a revoked, expired or unknown key is 401. A partner key with `Kirora-Workspace` names that tenant as `workspace`.

## Returns

Returns `200 OK` with a `ApiCaller` in `data`. Otherwise returns an error; [Errors](/docs/api/errors) lists every code and which to retry.

- `workspace` (object, required) — The workspace the request acts in.
  - `id` (string, required, uuid)
  - `name` (string, required)
- `apiKey` (object, required) — The key making the request.
  - `id` (string, required, uuid)
  - `name` (string, required)
  - `kind` (string, required, one of `integration`, `agent`, `partner`) — `agent` keys cannot send; see the agents guide.
  - `source` (string | null, required, one of `zapier`, `make`, `n8n`, `http_api`) — The integration the key was made for, if any.
  - `scopes` (string[], required) — What the key may do.

## Example

```bash
curl https://api.kirora.io/v1/me \
  -H "Authorization: Bearer $KIRORA_API_KEY"
```

Response `200`:

```json
{
  "data": {
    "workspace": {
      "id": "018f2a4e-6b1c-7d3e-9f40-37386ae05a6b",
      "name": "Weekend specials"
    },
    "apiKey": {
      "id": "018f2a4e-6b1c-7d3e-9f40-37386ae05a6b",
      "name": "Weekend specials",
      "kind": "integration",
      "source": "zapier",
      "scopes": [
        "campaigns:read"
      ]
    }
  }
}
```