Skip to main content
GET
/
api
/
teams
/
{id}
/
members
List a team's members
curl --request GET \
  --url https://archyon.app/api/teams/{id}/members \
  --header 'Authorization: Bearer <token>'
{
  "members": [
    {
      "teamId": "<string>",
      "personId": "<string>",
      "addedAt": 123,
      "addedBy": 123,
      "person": {
        "id": "<string>",
        "name": "<string>",
        "email": "<string>",
        "photoUrl": "<string>",
        "title": "<string>"
      }
    }
  ]
}

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

Response

OK.

​
members
object[]
required