# Show who this connection is

> Who this connection is: its own access, the account, authentication, expiry, what it may do.

- Effect: Read - Changes nothing.
- Idempotent: yes
- Stability: stable
- MCP tool: `manitu_whoami` on https://mcp.manitu.de/mcp
- REST: `POST https://api.manitu.de/v1/whoami`
- Page: /reference/whoami/

## MCP tool

`manitu_whoami`

### Description for the model

Says who this connection is: the access, its account, its rights - which manitu customer account it works in, and through which access: the account id (it is also the customer number the account holder knows), the access id (main or sub access), how the connection authenticated, and until when; for an API key also what it may do (app_credential_level: read only, or write), what it may change without asking the user first, and until when (self_approval: level, expires_at), and which ways in it can use (rest, mcp). Call it first when you need to know whose account you act in, before telling the user which account a later answer refers to, or when a change is refused and you need to know whether this connection may change anything at all. Another access of the account, by its access_id: [`manitu_account_access_get`](/reference/account/access/get.md); all of them: [`manitu_account_access_list`](/reference/account/access/list.md). It also counts the unread notices manitu left for this access in the customer panel, and the urgent ones among them (read them with [`manitu_access_notice_list`](/reference/access/notice/list.md)). How many calls this access has left: [`manitu_access_rate_limit_get`](/reference/access/rate-limit/get.md). It returns no contact or contract data - no name, no address, no products.

### Arguments

Takes no arguments.

### Example

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "manitu_whoami",
    "arguments": {}
  }
}
```

## REST

`POST https://api.manitu.de/v1/whoami`

### Description

Says who the connection is: the access the call is made with, the manitu customer account it belongs to, and its rights - the account id (also the customer number), the access id (main or sub access), how the credential authenticated (credential_type, auth_strength) and until when (expires_at); for an API key also its level (app_credential_level: read or write), what it may change without a person's approval in the customer panel and until when (self_approval: level, expires_at) and the ways in it can use now (usable_channel_list). It counts the unread notices manitu left for the access in the customer panel, and the urgent ones among them ([`POST /v1/access/notice/list`](/reference/access/notice/list.md)). Another access of the account, by its access_id, is [`POST /v1/account/access/get`](/reference/account/access/get.md); the rate limits, [`POST /v1/access/rate-limit/get`](/reference/access/rate-limit/get.md). No contact or contract data. Changes nothing.

### Authentication

One of `X-API-Key`, `Authorization: Bearer …` - never more than one in a request.

### Request body

JSON; unknown fields are refused.

No fields - send {} or no body.

### Response

In `data`; the rest of the body as on every call.

- `account_id` (integer, required) - The customer account - its id is also its customer number.
- `access_id` (integer, required) - The access on that account this call is made with.
- `credential_type` (string, required) - What this call was made with. (one of `"session"`, `"apikey"`, `"oauth"`)
- `auth_strength` (string, required) - How the access authenticated. (one of `"password"`, `"tfa"`, `"token"`, `"oauth"`)
- `expires_at` (string | null, required) - When the credential ends at the latest (ISO 8601), or null. (pattern `"^[^\\x00-\\x1F\\x7F]*$"`)
- `app_credential_level` (string | null, required) - What an API key may do: read only, or write. What a key may do without the user's approval is set for the key in the customer panel; what needs his approval there waits for him. null for a session. (one of `"read"`, `"write"`, `null`)
- `self_approval` (object, required) - What the key may change without being asked, and until when - set for it by the user in the customer panel; both null without a key.
  - `self_approval.level` (string | null, required) - The higher, the less is asked: client_dialog (the default) - a change that needs the user's yes is answered with approval_required and an approval_token, and goes through as the same call again with it after his yes in the chat; caller_confirmation - such changes go through without that round, the user trusts this key with them; client_click - also what would need a confirmation in a window of his client. Terms and prices are asked for each time, and what needs a person in the customer panel waits there, whatever the key may do. The level that holds now: client_dialog once expires_at has passed; null without a key. (one of `"client_dialog"`, `"caller_confirmation"`, `"client_click"`, `null`)
  - `self_approval.expires_at` (string | null, required) - Until when level holds, client_dialog after it; null: without end or without a key. (format `date-time`)
- `facade` (string | null, required) - The way this call came: rest or mcp; null if not known. (one of `"rest"`, `"mcp"`, `null`)
- `usable_channel_list` (array of string, required) - The ways in this credential can use now: rest and mcp for a key; panel for a session - its sign-in to the customer panel, which also covers calls made with the session over REST (a session never works over MCP). A way not listed is closed for it - the user sets the ways in in the customer panel.
- `notice` (object | null, required) - The notices manitu left for this access in the customer panel (read them with [`POST /v1/access/notice/list`](/reference/access/notice/list.md)); null if they could not be read.
  - `notice.count` (object, required)
    - `notice.count.new` (object, required) - The unread ones.
      - `notice.count.new.all` (integer, required) - All unread notices.
      - `notice.count.new.urgent` (integer, required) - Of those, the urgent ones - worth telling the user about once.

### Statuses

- `200` Success.
- `400` The input is wrong, or the request itself (INVALID_INPUT). Each entry names its field and its reason - correct the input and call again.
- `401` No credential was presented, or it was not recognised (UNAUTHENTICATED).
- `403` The credential is valid, but may not do this (PERMISSION_DENIED). The reason says why - another credential is the way, not a repeat.
- `429` Too many calls. The Retry-After header says when to try again.
- `500` The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.
- `503` The channel this operation forwards through is unavailable.

### Example

```sh
curl -X POST \
  'https://api.manitu.de/v1/whoami' \
  -H "X-API-Key: $API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{}'
```

## Example result

```json
{
  "account_id": 12345,
  "access_id": 12345,
  "credential_type": "session",
  "auth_strength": "password",
  "expires_at": "2026-10-23T12:00:00+02:00",
  "app_credential_level": "read",
  "self_approval": {
    "level": "client_dialog",
    "expires_at": "2026-10-23T12:00:00+02:00"
  },
  "facade": "rest",
  "usable_channel_list": [
    "panel"
  ],
  "notice": {
    "count": {
      "new": {
        "all": 1,
        "urgent": 1
      }
    }
  }
}
```
