Renames an Application, or changes its slug.
Updates the Application's operator-facing display name and/or its slug. Applies immediately and everywhere the name is rendered — the name is never copied into other rows. A rename leaves the slug alone: the slug is what every shared link is built from, so it changes only when the request names it, and doing so breaks links built on the old one. A slug already in use in the tenant is a 409. Ownership of the Agents and Workflows the Application holds is immutable and cannot be changed here. The Default Application can be renamed: it is the default because of its flag, not because of its name.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The Application id or slug to update.
The tenant identifier
The new name and/or slug.
When present, the new operator-facing display name. Trimmed; must not be blank.
When present, the new URL-safe identifier. Must be canonical and free within the tenant. Every existing link built on the old slug stops resolving — this is a deliberate write, never a side effect of a rename.
When present, whether a sender this Application refuses is told their message is being looked at rather than met with silence (Network.AcknowledgeRefusedSenders). Off unless set: an auto-reply to every unrecognized inbound is a spam and cost surface on a public channel.
When present, whether a sender is told their access request was approved (Network.NotifyApprovedSenders). On unless turned off.
When present, whether this Application's agents may read their sender's conversations with its other agents (Network.SenderConversationsAcrossAgents). On unless turned off.
When present, what this Application does with a sender no directory identity matches. InboundAdmissionPolicy.RequestAccess queues them for a human; InboundAdmissionPolicy.Reject ignores them entirely — no run, no queue entry, and nothing retained.
"UNSPECIFIED" | "REQUEST_ACCESS" | "REJECT" | "PROVISION"When present, the same choice for a known contact holding no grant here. Separate from UpdateNetworkRequest.UnknownSenderAdmission because they are different decisions.
"UNSPECIFIED" | "REQUEST_ACCESS" | "REJECT" | "PROVISION"When present, the escalation desk for conversations that came through none of this Application's channels — the web widget, the test console. Must be an operator desk of this Application. Use UpdateNetworkRequest.ClearOtherConversationsEscalationDesk for no handoff on them.
uuidResponse Body
curl -X PATCH "https://api.fruxon.com/v1/tenants/string/networks/string" \ -H "Content-Type: application/json" \ -d '{}'{
"id": "00000000-0000-0000-0000-000000000000",
"name": "string",
"slug": "string",
"isDefault": false,
"acknowledgeRefusedSenders": false,
"notifyApprovedSenders": false,
"senderConversationsAcrossAgents": false,
"unknownSenderAdmission": "REQUEST_ACCESS",
"knownUnenrolledAdmission": "REQUEST_ACCESS",
"otherConversationsEscalationDeskId": "00000000-0000-0000-0000-000000000000",
"createdAt": 0,
"modifiedAt": 0,
"members": [
{
"id": "00000000-0000-0000-0000-000000000000",
"networkId": "00000000-0000-0000-0000-000000000000",
"agentId": "string",
"operationalStatus": "ACTIVE",
"createdAt": 0,
"modifiedAt": 0
}
]
}{
"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
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Grants a participant access to the Network.
The participant must exist and be a person or group; an AI agent is a member, not a served participant, and yields `400 Bad Request`. Idempotent: granting an existing participant again re-applies its relationship and per-customer policy and reactivates a revoked grant. Applies immediately.
Projects the Network's people with their composable role badges and provenance.
Returns every participant that holds any live relationship in the Network — an active access grant, an active operator membership, or a consult-allowed member edge — with their additive role badges. Each badge exposes the source relationship (access grant / operator membership / member relation) that granted it, so the UI can render "why" and offer a narrow, badge-scoped revoke. Pass badge to filter to one composable view (`CUSTOMER`, `INTERNAL`, `OBSERVER`, `OPERATOR`, `ADVISOR`, or `CHANNEL`); the returned counts always reflect the full projection so every tab shows its total.