Returns the calling user's effective role on the agent.
The role resolves through the agent's owning Application, unioned with any legacy per-agent grant and with tenant-admin status. `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. Deliberately **not** 403 on denial — "you have no access" is an answer this endpoint has to be able to give, so an agent the caller cannot reach is a 200 with a null role. Only an agent that does not exist is a 404. Soft-deleted agents still resolve during their grace period.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The agent ID.
The tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/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
}API Reference
Previous Page
Activates an agent
Flips the agent's `Enabled` flag to true so connectors and scheduled triggers will route executions to it. The agent must already have a deployed revision; activation alone does not build or deploy flow content. Idempotent — calling it on an already-enabled agent simply returns the current state. Pair with `POST /v1/tenants/{tenant}/agents/{agent}:deactivate` to pause traffic without deleting. Returns 400 for an agent scheduled for deletion — cancel the deletion first with `POST /v1/tenants/{tenant}/agents/{agent}:cancelDelete`, which restores its previous state.