Skip to main content
GET
/
api
/
workspaces
/
{id}
/
members
List workspace members
curl --request GET \
  --url https://archyon.app/api/workspaces/{id}/members \
  --header 'Authorization: Bearer <token>'
{
  "members": [
    {
      "userId": 123,
      "workspaceId": "<string>",
      "addedAt": 123,
      "user": {
        "id": 123,
        "displayName": "<string>",
        "login": "<string>",
        "avatarUrl": "<string>",
        "provider": "<string>"
      },
      "addedBy": 123
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.archyon.app/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Both Clerk session JWTs (browser) and Archyon Personal Access Tokens (an_pat_…, server / CLI / MCP) use the same Bearer header. The server distinguishes them by token shape.

  • Clerk JWTs carry org context in the token claims (org_id, org_role, org_slug) — required for org-scoped endpoints. Configure your Clerk session template to include these claims; see DEPLOYMENT.md.
  • PATs are minted at /account → Tokens. Each PAT is bound to whichever org was active at mint time. Switch orgs and re-mint to address a different org.

Path Parameters

​
id
string
required

Workspace id (slug-like; provided at create time).

Response

200 - application/json

OK.

​
members
object[]
required
​
myRole
enum<string>
required
Available options:
owner,
editor,
viewer