FruxonDocs
AgentsCore

Deletes an Agent through its canonical owning Application.

Soft-deletes the Agent — it stops serving traffic but stays readable within the deletion grace period before it is purged. The lookup is scoped to the Application in the route, so an Agent owned by a different Application returns 404. Requires the Admin role.

DELETE
/v1/tenants/{tenant}/networks/{network}/agents/{agent}

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

network*string

Id of the owning Application.

Formatuuid
agent*string

Id of the Agent to delete.

tenant*string

The tenant identifier

Response Body

curl -X DELETE "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/agents/string"
Empty
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Lists the Agents canonically owned by an Application.

Returns only the Agents whose canonical owner is the Application in the route — unlike `GET /v1/tenants/{tenant}/agents`, which spans every Application the caller can reach. The response is cursor-paginated and the caller needs at least the Viewer role on the Application. Returns 404 if the Application does not exist or is not accessible.

Creates an Agent canonically owned by the Application in the route.

The Application in the route wins — any owner supplied in the body is overwritten before validation, so an Agent can never be created into a different Application than the one the caller was authorized against. Requires the Editor role. Responds 201 with a `Location` header pointing at the new Agent, or 400 with per-field validation errors.