Skip to main content
POST
Assign member position

Authorizations

Authorization
string
header
required

Clerk session JWT (deployments with Clerk auth) — validated per request (issuer + signature + lifetime + authorized-party). The internal Boardy tenant/member are resolved from the token's ACTIVE Clerk organization (org_id) → the Boardy tenant it maps to → this user's member in that tenant (#356). A token with no active organization is rejected; production never trusts spoofable X-Tenant-Id/X-Member-Id headers. The same normalized context backs the SPA, this OpenAPI surface, and MCP.

Headers

Idempotency-Key
string

AD-5 idempotency: a repeated mutation with the same key replays the prior result (no double-apply).

Path Parameters

id
string<uuid>
required

Body

application/json
positionId
null | string<uuid>
required

Response

OK

id
string<uuid>
required
tenantId
string<uuid>
required
email
string
required
kind
enum<string>
required
Available options:
Human,
Agent,
System
authMethod
string
required
role
enum<string>
required
Available options:
Owner,
Member
status
enum<string>
default:Active
Available options:
Active,
Suspended
displayName
null | string
positionId
null | string<uuid>
authorityEpoch
default:0
name
null | string