Retrieves a specific access request.
Returns a single onboarding request raised by a chat user against the given agent, including its current `status` (`Pending`, `Approved`, or `Rejected`) and any note recorded by the reviewer. Scoped to the agent — the request id is only valid in combination with the agent it was filed against. Requires the caller to have access to the agent. Use `POST .../{accessRequest}:approve` or `:reject` to act on a pending request.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The agent identifier.
The access request ID.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/chatUserAccessRequests/497f6eca-6276-4993-bfeb-53cbbbba6f08"{
"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
}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`.
Rejects an access request.
The chat user remains in onboarding status after rejection.