Skip to content
AiKYNETIX

Add clients to a group

POST
/api/client-groups/{id}/members/
curl --request POST \
  --url http://localhost:8000/api/client-groups/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/members/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "client_ids": [ "a1f1c0a2-0000-4000-8000-0000000000aa", "a1f1c0a2-0000-4000-8000-0000000000bb" ] }'

Add one or more clients to the group (idempotent). Every client_id must belong to the same team — an unknown or other-team id rejects the whole batch with 400. Returns the updated group.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
id
required
string format: uuid

Request Bodyrequired

Section titled “Request Bodyrequired”

Request body for adding clients to a group: a non-empty list of client UUIDs (all must belong to the same team — enforced in the service).

object
client_ids
required

Client UUIDs to add to the group.

Array<string>
Examples
ExampleAddTwoAthletes

Add two athletes

{
  "client_ids": [
    "a1f1c0a2-0000-4000-8000-0000000000aa",
    "a1f1c0a2-0000-4000-8000-0000000000bb"
  ]
}

Responses

Section titled “Responses”

200

Section titled “200”
Media typeapplication/json

A team-scoped client group (#545). name / description / colour are writable on create + PATCH; the roster (member_ids) is read-only here — mutate it via the /members/ endpoints. member_count powers the board column header without a second round-trip.

object
id
required
string format: uuid
name
required

Group name. Required; unique within the team.

string
<= 120 characters
description

Optional free-text description of the group.

string
<= 500 characters
colour

Optional UI tint — a design-token key (e.g. tone-recovery) or empty. Cosmetic; the board falls back to a deterministic colour.

string
<= 32 characters
member_ids
required

UUIDs of the clients in this group (many-to-many).

Array<string>
member_count
required

Number of clients in the group.

integer
created_at
required
string format: date-time
updated_at
required
string format: date-time
Examplegenerated
{
  "name": "example",
  "description": "example",
  "colour": "example"
}

400

Section titled “400”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}

401

Section titled “401”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}

404

Section titled “404”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}