> ## Documentation Index > Fetch the complete documentation index at: /docs/llms.txt > Use this file to discover all available pages before exploring further. # List alert triggers > Returns the trigger history of an alert, newest first. A trigger is one breach incident: it opens when the threshold is first crossed and resolves when the value recovers. > [!NOTE] > > **Guia relacionado**: Guia de alertas. Consulte o [Guia de alertas](/docs/pt-BR/ai-studio/observability/alerts.md) para ver um passo a passo com exemplos. ## OpenAPI ````yaml get /v2/alerts/{alert_id}/triggers openapi: 3.1.0 info: title: Toqan Router API version: '2.0' description: Toqan Router API documentation servers: - url: https://router.toqan.ai/eu description: Frankfurt (Europe) - url: https://router.toqan.ai/br description: São Paulo (Brazil) security: - ApiKey: [] tags: - description: >- API keys authenticate programmatic access to the workspace. They expose opaque tokens, per-domain access grants, and budget and rate-limit constraints. name: API keys - name: Logs description: >- OpenTelemetry log query API. Search, filter, aggregate, and facet log records ingested via OTLP. - name: Reporting description: >- GenAI reporting API over canonical analytics rollups. Accepts a metric name, time range, grain, group-by, and filters; returns a typed time series and optional totals. - name: Telemetry description: >- Unified query envelope for traces, metrics, and logs. One request shape, one filter dialect, and one response shape per source, validated by a per-source registry. - name: Traces description: >- Query and inspect ingested trace data: search trace summaries, aggregate metrics, and read individual traces and their spans. - name: Views description: Saved filters and columns for workspace observability pages. - description: List models available through the AI Router. name: Models - name: Alerts description: >- Alerts evaluate a telemetry metric on a fixed interval and fire notifications through notifiers when the value breaches a threshold. Each breach opens a trigger that tracks the incident until the value recovers. - name: Annotation Queues description: Annotation queues collect spans for human review. - name: Budgets description: >- Budgets govern spend, token usage, and request rate across six scopes: workspace, project, identity, API key, provider, and model. Every applicable budget is enforced, and the most restrictive limit applies per dimension. - name: Files description: File upload and retrieval operations. - name: Guardrail Rules description: >- Guardrail Rules conditionally enforce evaluators and plugins for AI Gateway traffic. Rules may be scoped to a project or the whole workspace. - name: Identities description: >- Identities represent end users from your system for usage and engagement tracking. - name: Management keys description: >- Management keys are workspace-scoped credentials that authenticate programmatic access to workspace administration surfaces (API keys, budgets). Unlike project-scoped API keys, a management key always operates at the workspace level. - name: MCP Gateway description: >- Register upstream MCP servers, discover and sync their tools, and assemble gateways that expose a curated tool surface to MCP clients. - name: Model Catalog description: >- Browse the Toqan Router model catalog: every model Toqan Router offers, across every provider, with pricing, capabilities and benchmark data. List endpoints only return models that are not deprecated. This API is public, requires no authentication, and is rate limited to 120 requests per minute per IP. Responses carry a 5-minute cache-control max-age. - name: Monitors description: >- Monitors are custom observability dashboards for traces, runtime metrics, and logs. Each monitor holds widgets that chart one telemetry query. List the metrics, operations, and dimensions available to your workspace with `GET /v3/telemetry/capabilities`, or start from a preset with `GET /v2/monitors/presets`. - name: Notifiers description: Notifier destinations used to send delivery and workflow notifications. - name: Routing Rules description: >- Routing Rules conditionally select models and enforce request plugins for AI Gateway traffic. Rules are evaluated by ascending priority and may be scoped to a project or the whole workspace. - name: Threads description: Threads group related trace invocations and their aggregate usage - name: Smart Routers description: >- Create and manage workspace Smart Routers. A Smart Router selects a model from an eligible pool for each request according to a quality, balanced, or cost profile. - name: Responses - name: Embeddings - description: Beta. Run typed classification questions against a classify model. name: Classify - description: Beta. Run classification decisions with the classify contract. name: Decisions - description: >- Run large offline workloads as JSONL batches and download OpenAI-compatible result files. name: Batches paths: /v2/alerts/{alert_id}/triggers: get: tags: - Alerts summary: List alert triggers description: >- Returns the trigger history of an alert, newest first. A trigger is one breach incident: it opens when the threshold is first crossed and resolves when the value recovers. operationId: AlertListTriggers parameters: - name: alert_id in: path description: Alert whose triggers to list. required: true schema: type: string - name: limit in: query description: Page size, 1-200. Unset uses the server default (25). schema: type: integer format: int32 - name: starting_after in: query description: |- Cursor for forward pagination. Set to the `trigger_id` of the last item from the previous page. schema: type: string - name: ending_before in: query description: |- Cursor for backward pagination. Set to the `trigger_id` of the first item from the previous page. schema: type: string responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/ListAlertTriggersResponse' '401': description: >- Authentication required. See https://router.toqan.ai/docs/reference/errors for the error codes. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: >- The resource does not exist. See https://router.toqan.ai/docs/reference/errors for the error codes. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - ApiKey: [] components: schemas: ListAlertTriggersResponse: required: - object - data - has_more type: object properties: object: type: string description: Object discriminator for list responses; always `list`. data: type: array items: $ref: '#/components/schemas/AlertTrigger' description: Page of triggers, ordered newest first. has_more: type: boolean description: |- Whether more triggers are available in the selected pagination direction. ErrorResponse: type: object properties: message: type: string description: Human-readable error message. code: type: integer description: Numeric error code, when one is available. details: type: array items: {} description: Additional error details, when the service reports any. required: - message AlertTrigger: required: - trigger_id - alert_id - project_id - status - opened_at - peak_value - last_value - event_count type: object properties: trigger_id: type: string description: Unique trigger identifier, for example `trigger_01H...`. alert_id: type: string description: Alert this trigger belongs to. project_id: type: string description: Project that owns the alert. status: enum: - open - resolved type: string description: Whether the breach is ongoing or recovered. severity: enum: - critical - degraded type: string description: Current tier of the incident. peak_severity: enum: - critical - degraded type: string description: Worst tier reached while the trigger was open. opened_at: type: string description: Time when the threshold was first crossed. format: date-time resolved_at: type: - string - 'null' description: Time when the value recovered. `null` while the trigger is open. format: date-time peak_value: type: number description: Worst observed value while the trigger was open. format: double last_value: type: number description: Most recent observed value. format: double event_count: type: integer description: Number of evaluation events recorded on this trigger. format: int32 query: allOf: - $ref: '#/components/schemas/AlertQuery' description: |- Query evaluated for this incident. Older incidents may omit it and inherit the alert's current query for display compatibility. AlertQuery: required: - metric type: object properties: metric: type: string description: >- Source-owned metric identifier. Trace metrics are validated against the Reporting catalogue; runtime metrics are validated against telemetry capabilities in the alert's scope. filters: type: array items: $ref: '#/components/schemas/MonitorFilter' description: Source-owned filters combined with AND. source: $ref: '#/components/schemas/AlertTelemetrySource' description: |- Telemetry source. Unspecified is accepted for compatibility and normalizes to traces when the alert is saved or read. operation: type: string description: |- Aggregation operation advertised by the selected metric capability. Existing trace queries may omit it; the server resolves their canonical Reporting operation. MonitorFilter: required: - field - op - values type: object properties: field: type: string description: |- Reporting dimension to filter on. Valid fields depend on the metric; validated when the monitor is saved. op: enum: - eq - neq - in - not_in - gt - gte - lt - lte - between - contains - exists - not_exists type: string description: >- Predicate operator. `eq` and `neq` accept exactly one value; `in` and `not_in` accept 1-100 values. values: type: array items: type: string description: Values compared against the selected field. AlertTelemetrySource: type: string enum: - ALERT_TELEMETRY_SOURCE_TRACES - ALERT_TELEMETRY_SOURCE_METRICS securitySchemes: ApiKey: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.