List alert fires
List recent alert FIRES across this workspace for a window (24h / 3d / 7d, default 24h), the same payload the Alerts review dashboard renders: total fires, how many distinct rules fired, the top-firing rule, a bucketed activity timeline, and the fired list (each fire's rule name, fired-at time, value, baseline, reason, delivery status, and the triggering call's sessionId). Use this to answer 'what alerts have fired lately / which rule is noisiest?'. To read or change the alert RULES themselves use list_alerts; this reads their firings. Workspace-scoped and read-only, it never re-scores a call or changes a rule.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/list_alert_fires" \ -H "Content-Type: application/json" \ -d '{ "agent": "string" }'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}List agent templates POST
List the agent templates a new agent can start from: tested agents kept in the template workspace (the inbound receptionist, speed-to-lead, review request and the rest of the set). Each has a `template` handle, the `name` a copy gets, a one-line description, its channels, its `section` (incoming, enquiries or customers) and its `direction` (inbound or outbound). Only agents a platform admin has listed with add_agent_template appear; an unlisted agent in the template workspace is a draft nobody sees. Read one in full with get_agent_template; start an agent from one with create_agent_from_template.
List alerts POST
List every alert rule configured in this workspace (trend + threshold) with its name, watched metricKey, alertType, enabled state, and delivery channel. Call this FIRST before create_alert so you don't duplicate a rule the workspace already has, and to answer 'what is being watched / what alerts are configured?'. Alerts are workspace-scoped statistical detectors over persisted metric values, they don't change the agent or re-score calls.