Accounts and me

# Accounts and me

Other endpoints take the account from the token, so you never send an account id. Use these two endpoints to check who the token acts as and which accounts that user belongs to.

## Endpoints

| Method and path | Does |
| --- | --- |
| `GET /api/v1/me` | Reads the user the token acts as |
| `GET /api/v1/accounts` | Lists the accounts that user belongs to |

Both need `api_read`. Unlike the other endpoints, they do not read the account from the token. They check `api_read` in the account named by an `account_id` query parameter (an account id from `GET /accounts`), or else in the user's first account. A user who belongs to several accounts can get `403 Insufficient API permissions` here while the token works on other endpoints. Add `?account_id=` with the token's account to avoid that. These two endpoints also accept an older token that has no account.

## GET /api/v1/me

Returns the user the token acts as. Use it to check that a token works and to see which person it acts as.

```bash
curl -H "Authorization: Bearer $DRUM_API_TOKEN" \
  https://app.getdrum.com/api/v1/me
```

Response (`200`):

```json
{
  "id": 118,
  "name": "Jordan Reed",
  "avatar_url": "https://www.gravatar.com/avatar/...",
  "sgid": "BAh7CEkiCGdpZAY6BkVU...",
  "content": "<span>\n  <img height=\"14\" width=\"14\" ...> Jordan Reed\n</span>\n"
}
```

| Field | Meaning |
| --- | --- |
| `id` | The user id. This is not a member id: to find the member, match `name` to `full_name` in [`GET /members`](/api/reference/lookup-lists/#members) |
| `name` | The user's name |
| `avatar_url` | A link to the user's picture, or a Gravatar link when they have not uploaded one |
| `sgid`, `content` | Used by Drum's own editor to mention the user. Ignore them |

The response has no email address, role or permissions.

## GET /api/v1/accounts

Returns every account the token's user is a member of, not only the token's own account. Accounts the user has been removed from are left out. Not paginated.

```bash
curl -H "Authorization: Bearer $DRUM_API_TOKEN" \
  https://app.getdrum.com/api/v1/accounts
```

Response (`200`):

```json
[
  {
    "id": "acct_7Kq2Lm9X",
    "name": "Riverside Engineering",
    "personal": false,
    "owner_id": 118,
    "created_at": "2024-03-02T01:12:44.000Z",
    "updated_at": "2026-08-30T22:05:10.000Z"
  }
]
```

| Field | Meaning |
| --- | --- |
| `id` | The account id, a string |
| `name` | The account name |
| `personal` | `true` for a personal account |
| `owner_id` | The user id of the account owner |
| `created_at`, `updated_at` | When the account was created and last changed |

The response does not list members. To look up members, with their names, emails, role and default resource type, use [`GET /members`](/api/reference/lookup-lists/#members). It needs the `read_account_users` permission.

Other endpoints take the account from the token, so you never send an account id. Use these two endpoints to check who the token acts as and which accounts that user belongs to.

Endpoints

Method and path	Does
`GET /api/v1/me`	Reads the user the token acts as
`GET /api/v1/accounts`	Lists the accounts that user belongs to

Both need api_read. Unlike the other endpoints, they do not read the account from the token. They check api_read in the account named by an account_id query parameter (an account id from GET /accounts), or else in the user’s first account. A user who belongs to several accounts can get 403 Insufficient API permissions here while the token works on other endpoints. Add ?account_id= with the token’s account to avoid that. These two endpoints also accept an older token that has no account.

GET /api/v1/me

Returns the user the token acts as. Use it to check that a token works and to see which person it acts as.

curl -H "Authorization: Bearer $DRUM_API_TOKEN" \
  https://app.getdrum.com/api/v1/me

Response (200):

{
  "id": 118,
  "name": "Jordan Reed",
  "avatar_url": "https://www.gravatar.com/avatar/...",
  "sgid": "BAh7CEkiCGdpZAY6BkVU...",
  "content": "<span>\n  <img height=\"14\" width=\"14\" ...> Jordan Reed\n</span>\n"
}

Field	Meaning
`id`	The user id. This is not a member id: to find the member, match `name` to `full_name` in `GET /members`
`name`	The user’s name
`avatar_url`	A link to the user’s picture, or a Gravatar link when they have not uploaded one
`sgid`, `content`	Used by Drum’s own editor to mention the user. Ignore them

The response has no email address, role or permissions.

GET /api/v1/accounts

Returns every account the token’s user is a member of, not only the token’s own account. Accounts the user has been removed from are left out. Not paginated.

curl -H "Authorization: Bearer $DRUM_API_TOKEN" \
  https://app.getdrum.com/api/v1/accounts

Response (200):

[
  {
    "id": "acct_7Kq2Lm9X",
    "name": "Riverside Engineering",
    "personal": false,
    "owner_id": 118,
    "created_at": "2024-03-02T01:12:44.000Z",
    "updated_at": "2026-08-30T22:05:10.000Z"
  }
]

Field	Meaning
`id`	The account id, a string
`name`	The account name
`personal`	`true` for a personal account
`owner_id`	The user id of the account owner
`created_at`, `updated_at`	When the account was created and last changed

The response does not list members. To look up members, with their names, emails, role and default resource type, use GET /members. It needs the read_account_users permission.