FruxonDocs
ConnectorsChat Users

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`.

POST
/v1/tenants/{tenant}/agents/{agent}/chatUserAccessRequests/{accessRequest}:approve
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

agent*string

The agent identifier.

accessRequest*string

The access request ID.

Formatuuid
tenant*string

The tenant identifier

Optional note about the approval.

note?string|null

Optional note explaining the decision.

[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string/chatUserAccessRequests/497f6eca-6276-4993-bfeb-53cbbbba6f08:approve" \  -H "Content-Type: application/json" \  -d '{}'
{
  "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
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}