---
title: "Get the users that can be mentioned in the notes of the brand's planner posts."
method: GET
path: "/v2/scheduler/notes/mentionable-users"
tags: ["Planner Notes Mentions Api Service"]
---

# Get the users that can be mentioned in the notes of the brand's planner posts.

`GET /v2/scheduler/notes/mentionable-users`

## Request

- Base URL: `https://app.metricool.com/api`
- URL: `https://app.metricool.com/api/v2/scheduler/notes/mentionable-users`
- Auth: none declared

Calendar and library: whoever can see the brand's posts. On a brand of an agency white-label that also covers the agency team members and the agency end clients. Deleted accounts are excluded. Rejected for sessions that cannot mention (integrator and white-label end clients, Vendasta and the anonymous reviewer). The whole list is returned: filtering by the typed text is done by the frontend over the loaded list.

To write a mention into the note content, interpolate the entry's `mentionId` and its `name` as `@[<mentionId>|<name>]`.

Use `mentionId` verbatim and never build it from `userId` or `agencyId`/`agencyUserId`: an agency end client has no `userId`, so composing the marker from it produces a marker the server cannot resolve and the mention is silently lost — the note saves, with no error, mentioning nobody.

Use `name` for the label. What is stored is taken from the mentioned account rather than from the request, because the label lives inside the note content and the content is served verbatim to every reader, including sessions that must not see email addresses. A label written beside an id this API cannot resolve is kept as sent, except for an email address, which is reduced to its local part.

## Response `200`

OK

- JsonOkListResponseMentionableUserDto
  - `metadata` object
  - `page` JsonPaging
    - `next` string
  - `data` MentionableUserDto[]
    - `mentionId` string: Id to write inside the mention marker of the note content, as @[<mentionId>|<name>]. Opaque and always present: interpolate it exactly as it arrives, never compose it from the id fields below. An agency end client has no userId, so a marker built from userId reads as @[null|...], which the server cannot resolve — the note saves but mentions nobody, with no error.
    - `userId` integer: Regular user id of the user. Absent for an agency end client.
    - `agencyId` integer: Agency id of the user. Only for an agency end client.
    - `agencyUserId` integer: Agency user id of the user. Only for an agency end client.
    - `label` 'CLIENT' | 'STAFF': Badge to show next to the user, relative to the requesting session: CLIENT (an agency end client, as seen by a Metricool session), STAFF (anyone who is not an agency end client, as seen by an agency end-client session), or absent for no badge.
    - `name` string: Display name of the user, and the value to use as the mention label. A nameless account — common, since invited collaborators and end clients have no name until they activate — falls back to the local part of its address, never the whole address, because this value ends up stored inside the note content.
    - `email` string: Email of the user, for display in the picker only. Omitted for agency end-client sessions, which must not see the emails of the agency staff nor of the other clients. Never use it as the mention label: the label is stored in the note content and served verbatim to readers who must not see addresses.
    - `profilePicture` string: Public URL of the user's 400x400 profile picture. Absent when they have none, in which case the frontend renders its initials fallback. Always absent for agency end clients — agency pictures are out of scope.

---

[API](https://skmtc.dev/metricool/apis/metricool-api.md) · [All operations](https://skmtc.dev/metricool/apis/metricool-api/llms.txt) · [OpenAPI document](https://skmtc.dev/metricool/apis/metricool-api/revisions/aea9d9a8415a?raw)