Lists the Network's operator directory.
Returns every enrolled operator in the Network (active and disabled), in participant order. The set is small and slow-changing, so it is returned as one page.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The owning Network id.
uuidThe tenant identifier
Query Parameters
The maximum number of items to return per page
int32int32Opaque cursor token from an external system (e.g. RAG API). When set, M:Fruxon.Common.Collections.PageToken.AsString returns this value directly instead of encoding Fruxon.Common.Collections.PageToken.Skip.
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/operators"{
"items": [
{
"id": "00000000-0000-0000-0000-000000000000",
"networkId": "00000000-0000-0000-0000-000000000000",
"participantId": "00000000-0000-0000-0000-000000000000",
"displayName": "string",
"status": "ACTIVE",
"presence": "AVAILABLE",
"presenceChangedAt": 0,
"presenceNote": "string",
"activeConversationCount": 0,
"roleKeys": [
"string"
],
"poolKey": "string",
"createdAt": 0,
"modifiedAt": 0
}
],
"nextPageToken": "string",
"totalCount": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Returns one served-participant grant by its participant id.
Looks up a single grant by participant id, returning its relationship, live status, and §17.8 per-customer policy. A participant id that has no grant in the Network yields `404 Not Found`.
Searches enrollable-operator candidates for the Add-operator picker.
A DB-paged, name-searchable page of curated directory Persons who could be enrolled as an operator here, each carrying the server's verdict: `status` (`ELIGIBLE` / `PROMOTABLE` — enrolling first classifies them as internal — / `INELIGIBLE`) and, when ineligible, a stable `ineligibleReason` code. Existing operators, external customers, disabled people, groups and ambient identities are all filtered out — nothing an admin can act on — so in practice every row is selectable. Holding a served (customer) grant in this Application is <b>not</b> a rejection: per design §3 an internal teammate may be served and an operator at once. The `servedHere` flag says so for display only. This backs the picker's server-side type-ahead so it no longer loads the whole tenant directory or the whole served set. The verdict is the same predicate the enroll path enforces, so a selectable candidate is one `POST` accepts. The literal `candidates` segment out-ranks the `{operator}` route, so there is no collision.