Members and directory API

6 endpoints.

Members#

Members come back as:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21

{
  "data": [
    {
      "participant_id": "5e4d…",
      "membership": "join",
      "power_level": 0,
      "joined_at": "2026-05-10T09:00:00Z",
      "notification_mode": "mentions",
      "muted_until": null,
      "response_mode": null,
      "participant": {
        "id": "5e4d…",
        "local_id": "alice",
        "server_name": "scaiwave.example.com",
        "display_name": "Alice",
        "participant_type": "human",
        "avatar_url": "..."
      }
    }
  ]
}

For invites, kicks, bans, see Rooms API.

Directory#

Tenant-scoped browse + search.

Query parameters#

/v1/directory/participants:

• q — search string (matches local_id, display_name, email).
• type — filter by participant type (human, model, helper, …).
• limit, offset.
• include_federated=true — search the federation directory too.

/v1/directory/rooms:

• q — search room name / topic.
• room_type — filter.
• limit, offset.

Aliases#

ScaiWave resolves wiki-link [[Alias]] to either a note or a participant. The directory's alias endpoint is what powers that resolution at the API level — used by the AI's find_note plugin and by the client when rendering a wiki-link click.

1
2

curl "$BASE/v1/directory/alias/Meeting%20Notes%202026-05-12" \
  -H "Authorization: Bearer $TOKEN"

Returns either a note reference or an error.