Access & visibility
Allow workspace.ListColleagues on your API key.
Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.
Request
No parameters. Send an empty JSON object ({}).
Response
Returns 200 OK with a JSON body.
This operation has no continuation cursor. An empty items array means no matching visible results were returned.
This is the active colleague roster for members with workspace access; chat-only guests cannot read it. Use account IDs for approved member delegation, not customer Person record IDs. Listing a colleague never grants the key authority to act as them.
itemsarray of ColleagueRequiredWorkspace colleagues with their account IDs and display names. This operation has no cursor pagination.
Item fields
idstringRequiredWorkspace member's account ID, which can be used with Brigg-Act-As only if this key's delegation grant permits that member.
namestringRequiredMember's display name.
rolestringRequiredBase role ID, such as owner, admin or member, or a workspace-defined role ID. It is not a localized label or a complete list of additive permissions. Resolve labels with workspace.ListRoles.
Errors & retries
This operation reads data. It needs no idempotency key and can be retried after a transient failure.
For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.
| HTTP status | Code | What to do |
|---|---|---|
| 400 | invalid_json |
Send a JSON object with Content-Type: application/json. |
| 400 | invalid_input |
Check the request fields and types. |
| 401 | invalid_key |
The workspace API key is missing, invalid or revoked. |
| 403 | forbidden |
Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member. |
| 404 | not_found |
The requested operation or resource is not available to this credential. |
| 429 | rate_limited |
Wait for Retry-After before retrying. |
Next steps
JSON schemas
Use the complete schemas for validation or client generation.
Full request JSON schema
{
"type": "object",
"properties": {},
"additionalProperties": false,
"examples": [
{}
]
}Full response JSON schema
{
"type": "object",
"properties": {
"items": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Workspace member's account ID, which can be used with Brigg-Act-As only if this key's delegation grant permits that member.",
"examples": [
"account_alex"
]
},
"name": {
"type": "string",
"description": "Member's display name.",
"examples": [
"Alex Morgan"
]
},
"role": {
"type": "string",
"description": "Base role ID, such as owner, admin or member, or a workspace-defined role ID. It is not a localized label or a complete list of additive permissions. Resolve labels with workspace.ListRoles.",
"examples": [
"member"
]
}
},
"required": [
"id",
"name",
"role"
],
"additionalProperties": false,
"title": "Colleague"
},
"description": "Workspace colleagues with their account IDs and display names. This operation has no cursor pagination."
}
},
"required": [
"items"
],
"additionalProperties": false,
"examples": [
{
"items": [
{
"id": "account_alex",
"name": "Alex Morgan",
"role": "member"
}
]
}
]
}