Get started

Organisation members

Source

List active organisation members, add or re-admit GitHub accounts on any plan, and soft-remove members with last-owner protection.

text
GET /api/v1/org/members
POST /api/v1/org/members
POST /api/v1/org/members/remove
text
Authorization: Bearer vitna_key_...
bash
curl -H "authorization: Bearer vitna_key_..." https://vitna.ai/api/v1/org/members

curl -X POST https://vitna.ai/api/v1/org/members \
  -H "authorization: Bearer vitna_key_..." \
  -H "content-type: application/json" \
  -d '{"github": "octocat", "role": "member"}'

Unlimited seats and last-owner protection

Every Vitna plan admits as many members as you like (seatAllowance: null): Vitna counts workloads, never seats. Reads (GET) accept either a platform or push key; writes (POST) require a platform key (vitna_key_...).

The invited GitHub handle must have signed in at /auth/github/start at least once so site.user holds a verified account id (404 user_not_signed_in otherwise).

Removing a member via POST /api/v1/org/members/remove dates removed_at and removed_reason rather than deleting the row, and refuses to remove the sole active owner (409 last_owner) so an organisation can never orphan itself.

Listing response

json
{
  "data": [
    {
      "orgId": "convexity",
      "userId": 1,
      "login": "garrett",
      "githubId": 1001,
      "name": "Garrett",
      "role": "owner",
      "addedAt": "2026-09-14T12:00:00.000Z"
    }
  ],
  "meta": {
    "generatedAt": "2026-09-14T12:00:00.000Z",
    "orgId": "convexity",
    "count": 1,
    "seatAllowance": null
  }
}