FruxonDocs
Agent NetworkParticipants

Rejects an access request.

Records the rejection on the row. Future inbound from the same sender creates a fresh pending row — reject means "no for now," not "never." A `:block` verb (deferred) would be the never form. Requires Editor role on the request's agent.

POST
/v1/tenants/{tenant}/participantAccessRequests/{participantAccessRequest}:reject

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

participantAccessRequest*string

The participant access request ID.

Formatuuid
tenant*string

The tenant identifier

Request Body

Optional note about the rejection.

note?string|null
Lengthlength <= 4000
[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/participantAccessRequests/497f6eca-6276-4993-bfeb-53cbbbba6f08:reject" \  -H "Content-Type: application/json" \  -d '{}'
{
  "id": "00000000-0000-0000-0000-000000000000",
  "integrationConfigId": "00000000-0000-0000-0000-000000000000",
  "provider": "string",
  "address": "string",
  "agentId": "string",
  "matchedParticipantId": "00000000-0000-0000-0000-000000000000",
  "networkId": "00000000-0000-0000-0000-000000000000",
  "displayName": "string",
  "conversationName": "string",
  "status": "PENDING",
  "processedBy": "string",
  "processedAt": 0,
  "processingNote": "string",
  "approvedParticipantId": "00000000-0000-0000-0000-000000000000",
  "capturedAttributes": {},
  "suggestedEnvironment": {
    "environmentId": "00000000-0000-0000-0000-000000000000",
    "displayName": "string",
    "isNew": false
  },
  "createdAt": 0,
  "modifiedAt": 0
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Retrieves a specific access request by ID.

Loads the full access request row for operator review, including the proposed sender channel, matched participant (when one was found), and processing metadata. Use this before approving or rejecting when the list view does not include enough context for the decision.

Lists the Applications (Networks) this participant belongs to, with role badges and per-customer policy.

The inverse of the per-Application `People & groups` list: for one participant it returns every Application they hold a live relationship in, each with the same composable role badges the Application's People projection shows (Customer / Internal / Operator / Advisor / Observer / Channel), the served relationship key, the §17.8 response mode (agent mode), and any per-customer dedicated-operator escalation override. Drives the Directory participant detail's Applications tab. Grants are managed on the Application surface — this endpoint is read-only. Returns 404 when the participant does not exist; an empty list when they exist but are in no Application.