# Users and applications

> Get the bot, its application, its servers and the gateway address.

Endpoints about the bot itself, its application, and where to connect.

## Get current bot

`GET /v1/users/@me`

Returns the bot's [user object](https://lammapp.sa/developers/api-reference#user-object).

```json
{ "id": "1234567890123456789", "username": "app_1234567890123456789", "name": "Scorekeeper", "avatar_id": null, "bot": true }
```

## Get current application

`GET /v1/applications/@me`

Returns the app the token belongs to.

| Field | Type | Notes |
| --- | --- | --- |
| `id` | string | The application id, used in install links |
| `name` | string | |
| `description` | string | |
| `review_state` | string | Whether Lamma has reviewed the app |
| `bot_user_id` | string | The bot account's user id |

## Get current bot servers

`GET /v1/users/@me/guilds`

The servers the app is installed in.

```json
[{ "id": "…", "name": "Weekend squad", "icon_id": null }]
```

## Get gateway

`GET /v1/gateway`

The address to open the [gateway](https://lammapp.sa/developers/gateway) WebSocket on.

```json
{ "url": "wss://lammapp.sa/v1/gateway" }
```

Lamma users can't be looked up by id or name through the API. A bot learns about people from the servers it is in: members, message authors and command users.