Skip to main content
POST
/
api
/
workspaces
/
{id}
/
members
Add a workspace member
curl --request POST \
  --url https://archyon.app/api/workspaces/{id}/members \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "userId": 123,
  "role": "viewer"
}
'
{
  "ok": "<unknown>"
}

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).

Body

application/json
​
userId
integer
required
​
role
enum<string>
default:viewer
Available options:
owner,
editor,
viewer

Response

OK.

​
ok
any
required