Returns the calling user's effective role on the Application.
Resolves the explicit collaborator grant, tenant-admin status, and the legacy per-agent grants that are still promoted Application-wide. `role` is null when the caller has no access; the `canView` / `canEdit` / `canManage` flags project that role onto the permission ladder so clients do not reimplement it — in particular, `canManage` is the correct gate for the collaborator admin UI, which the API enforces as Application Admin rather than a tenant-wide scope. Deliberately **not** 403 on denial — "you have no access" is an answer this endpoint has to be able to give, so an Application the caller cannot reach is a 200 with a null role. Only an Application that does not exist is a 404.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The Application id.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/access"{
"role": "VIEWER",
"canView": false,
"canEdit": false,
"canManage": false,
"applicationId": "00000000-0000-0000-0000-000000000000",
"requestPending": false
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists the Applications visible to the current principal (Default first).
Returns every Application the current principal can access, Default first, without the member roster (fetch a single Application for its members). One page; the set is small and slow-changing.
Live operational counts for the Application, as of now.
Runs in flight per origin, approvals parked on a human, escalations awaiting a human, and pending participant admissions. Access requests are counted once per Application rather than per agent — approving one grants access across every member. Counts scope on each row's own Application attribution, the same join key the cost and automation rollups on this page use.