Lists access requests for an agent.
Optionally filter by status using the `status` query parameter.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The agent identifier.
The tenant identifier
Query Parameters
Filter by status (Pending, Approved, Rejected). Omit to return requests with any status.
"UNSPECIFIED" | "PENDING" | "APPROVED" | "REJECTED"Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/chatUserAccessRequests"[
{
"id": "00000000-0000-0000-0000-000000000000",
"provider": "string",
"identifier": "string",
"userName": "string",
"agentId": "string",
"connectorId": "00000000-0000-0000-0000-000000000000",
"conversationName": "string",
"status": "PENDING",
"processedBy": "string",
"processedAt": 0,
"processingNote": "string",
"tenantId": "00000000-0000-0000-0000-000000000000",
"createdAt": 0,
"modifiedAt": 0
}
]{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Update an existing evaluation metric.
Mutates the metric in place — every agent currently opted-in picks up the new prompt/weight on the next eval run. Use `POST EvaluationMetricDeprecate` instead of editing when you want to retire a metric without breaking historical comparability. System (non-LLM-judge) metrics cannot be edited and will return 400.
Approves an access request and activates the chat user.
Transitions the access request from `Pending` to `Approved` and activates the chat user so they can interact with the agent. Returns 400 if the request is not in `Pending` status — approve/reject are not retryable once a terminal decision has been recorded. Requires `Editor` role on the agent. The optional note is stored on the request for audit purposes and is visible to other reviewers via `GET .../{accessRequest}`. To deny access instead, use `POST .../{accessRequest}:reject`.