Fired / failed / blocked counts for the Application's automations over an optional window.
Counts `AgentExecutionRecord` rows fired by a trigger and stamped with this Application: `fired` = runs that started, `failed` = of those, runs that errored, `blocked` = attempts rejected at the pre-flight gate (budget / credits / license) that never ran. `from`/`to` are Unix ms (half-open); omitting them counts all time.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The Application (Network) id.
uuidThe tenant identifier
Query Parameters
Window start, Unix ms inclusive. Unbounded when omitted.
int64Window end, Unix ms exclusive. Unbounded when omitted.
int64Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/automations"{
"fired": 0,
"failed": 0,
"blocked": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}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.
Lists the live capability instances materialized for a Network.
Returns the operational capabilities materialized for the Network (for example SUPPORT_CASES), each badged with its live enablement and configuration. The supported capability set is small and fixed, so it is returned as a single page. Changes here apply immediately, without publishing a new Network revision.