Lists access requests in the tenant, filterable by agent / status / matched-or-approved participant.
The Agent Network overview tab calls this with `agentId` set to the current agent and `status=pending` to render the pending queue. The tenant-level triage page calls it without filters. Returns every match — paging is intentionally not modelled in v1 because the pending queue is bounded by operator throughput, not message volume.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The tenant identifier
Query Parameters
Narrow to requests against a single agent. Used by the agent-overview tab.
Filter by lifecycle status (Pending / Approved / Rejected). Omit for all.
"UNSPECIFIED" | "PENDING" | "APPROVED" | "REJECTED"Narrow to requests touching a specific participant — matches either matchedParticipantId (pending) or approvedParticipantId (committed). Useful for audit.
uuidResponse Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/participantAccessRequests"[
{
"id": "00000000-0000-0000-0000-000000000000",
"integrationConfigId": "00000000-0000-0000-0000-000000000000",
"provider": "string",
"address": "string",
"agentId": "string",
"matchedParticipantId": "00000000-0000-0000-0000-000000000000",
"displayName": "string",
"conversationName": "string",
"status": "PENDING",
"processedBy": "string",
"processedAt": 0,
"processingNote": "string",
"approvedParticipantId": "00000000-0000-0000-0000-000000000000",
"createdAt": 0,
"modifiedAt": 0
}
]{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists participants in the tenant
Returns every participant in the tenant, each with its inline channels and current agent bindings. Pass `agentId` to narrow the result to the participants bound to a single agent — the Agent Network UI uses this to render an agent's contact list. The result is unpaged.
Approves an access request and materializes the proposed addition to the participant graph.
Body's `mode` picks the commit shape: <list type="bullet"><item><b>createNew</b> — create a new Person participant from the observed sender, with one channel `{integrationConfigId, address}` from the request, and bind it to the request's agent.</item><item><b>addToExisting</b> — append the channel to an operator-chosen existing participant (`participantId` required) and ensure the binding to the request's agent.</item><item><b>bindOnly</b> — write just the agent binding; the channel already exists on the matched participant.</item></list> Returns 400 if the request is not in Pending, or if the requested mode is missing the field it requires (e.g. `bindOnly` on a request without a matched participant). Requires Editor role on the request's agent — enforced inside the service since the route doesn't carry the agent id.