The tenant's roster — humans and agents (what `@name` resolves against)

GET

/team

curl --request GET \
  --url https://quikstik-core.fly.dev/team \
  --header 'Authorization: Bearer <token>' \
  --header 'x-tenant-id: 2489E9AD-2EE2-8E00-8EC9-32D5F69181C0'

• Production

. The client resolves a typed @name to a participant_id from this list and sends the ids in a note’s mentions; the server never matches names. Humans are listed by their operator user id; the comms agent is agent:comms (enabled is the reviewer’s switch). Session, or an operator key with participants.read; a customer session is 404.

Authorizations

• bearerAuth
• operatorKey

Parameters

Header Parameters

x-tenant-id

required

string format: uuid

Tenant identifier (UUID).

Authn/authz semantics are intentionally TBD for this contract slice; this header exists to keep the contract explicitly multi-tenant from day 0.

Responses

200

The roster.

Media typeapplication/json

object

members

required

Array<object>

object

participant_id

required

The id a note’s mentions carries: an operator’s user id, or agent:comms.

string

display_name

required

string

kind

required

string

Allowed values: human agent

role

required

string

enabled

required

An agent’s switch; false for a human unless the roster says otherwise.

boolean

agent_may_pin

: may this agent write to a board? Default false — nothing automated writes to a human’s board. An agent’s POST /boards/{id}/sticks without it is 403 agent_may_not_pin.

boolean

aliases

: the names the member answers to besides its id (agent, chat, bot, …), lower-case. A note’s mentions accepts any of them, case-insensitively; an @word in a note’s text that matches exactly one member’s alias (or first name) is resolved by the server.

Array<string>

Example

{
  "members": [
    {
      "kind": "human"
    }
  ]
}

401

Missing or invalid session bearer token

Media typeapplication/json

object

reason

required

Stable, machine-readable reason code (e.g. “sold_out”, “processor_not_configured”, “rail_refused”).

string

Example

{
  "reason": "sold_out"
}

403

The session’s effect authority does not cover this operation

Media typeapplication/json

object

reason

required

Stable, machine-readable reason code (e.g. “sold_out”, “processor_not_configured”, “rail_refused”).

string

Example

{
  "reason": "sold_out"
}

404

Expired, consumed, unknown, or unresolvable — indistinguishable by design

Media typeapplication/json

object

reason

required

string

Example ^generated

{
  "reason": "example"
}

503

No durable backend is wired for this operation (fail-closed)

Media typeapplication/json

object

reason

required

Stable, machine-readable reason code (e.g. “sold_out”, “processor_not_configured”, “rail_refused”).

string

Example

{
  "reason": "sold_out"
}