People

Some writes name a person. Telling one individual about an announcement is the case that needs it: the audience entry takes that person’s id, and a name is not one. This endpoint turns a name or an email into an id. To list the whole directory, with roles, teams and who reports to whom, see Members.

Find people

GET /v1/people

Members of the organization whose name or email matches query. It includes members who hold no role and are on no team, which the org chart and team rosters leave out.

Query parameters

Parameter	Type	Notes
query	string	Matches anywhere in the name or the email, case-insensitively. Leave it out to list people.
limit	integer	At most this many people, 1 to 50. Defaults to 25.

Note

There is no cursor. The endpoint is for finding a person, not for exporting the directory, so it returns the closest matches and nextCursor is always null. Narrow with query rather than paging.

Request

curl "https://api.mereon.ai/v1/people?query=ada" \
  -H "Authorization: Bearer $MEREON_TOKEN"

Response

{
  "data": [
    { "id": "usr_2d9e...", "name": "Ada Admin", "email": "ada@example.com" }
  ],
  "nextCursor": null
}

Who you can see

The endpoint sees what the connected user can see, evaluated on every request. An admin sees everyone in the organization. A user who is limited to their teams sees the people on them, and a user with no team visibility sees only themselves.

Using an id

Pass id as the actorId of an INDIVIDUAL announcement audience entry. See Announcements.

List teams

GET /v1/teams

The organization’s teams and their current members. Telling a whole team about an announcement takes the team’s id as the actorId of a TEAM audience entry, and this is where that id comes from.

Request

curl "https://api.mereon.ai/v1/teams" \
  -H "Authorization: Bearer $MEREON_TOKEN"

Response

{
  "data": [
    {
      "id": "team_5b2e...",
      "name": "Service crew",
      "members": [
        { "id": "usr_2d9e...", "name": "Ada Admin", "email": "ada@example.com" }
      ]
    }
  ],
  "nextCursor": null
}

Teams are scoped the way the teams page is. An organization admin sees every team, a team admin sees the teams they administer, and anyone else sees none. Every team you can see is returned, so nextCursor is always null.