report_get
Read-only
Retrieve scheduled Zabbix reports by report ID or dashboard ID. Find all reports generated from specific dashboards for auditing and delivery tracking.
Instructions
Retrieve scheduled reports. Reports are generated from dashboards on a schedule and delivered to users or user groups via email or other media. Filter by reportids for direct lookup or by dashboardids to find all reports generated from specific dashboards.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return. | |
| filter | No | Return only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: active_since (6.0+), active_till (6.0+), cycle (6.0+), dashboardid (6.0+), info (6.0+), lastsent (6.0+), message (6.0+), name (6.0+), period (6.0+), reportid (6.0+), start_time (6.0+), state (6.0+), status (6.0+), subject (6.0+), userid (6.0+), weekdays (6.0+). Text properties cannot be filtered; use 'search' for them. | |
| output | No | Properties of the report object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: reportid, name, status. Properties: active_since (6.0+), active_till (6.0+), cycle (6.0+), dashboardid (6.0+), description (6.0+), info (6.0+), lastsent (6.0+), message (6.0+), name (6.0+), period (6.0+), reportid (6.0+), start_time (6.0+), state (6.0+), status (6.0+), subject (6.0+), userid (6.0+), weekdays (6.0+). | |
| search | No | Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: active_since (6.0+), active_till (6.0+), description (6.0+), info (6.0+), message (6.0+), name (6.0+), subject (6.0+). | |
| server | No | Target Zabbix server. Available: default. Defaults to 'default' if omitted. | |
| raw_json | No | Strips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true. | |
| reportids | No | Return only reports with the given IDs. | |
| sortfield | No | Sort by one or more of: reportid, name, status (comma-separated for several; pair with 'sortorder'). No other property is sortable. | |
| sortorder | No | Sort order: 'ASC' (ascending) or 'DESC' (descending). | |
| countOutput | No | Return the count of matching results instead of the actual data. | |
| searchByAny | No | If true, return results matching ANY search field (OR). Default is ALL fields (AND). | |
| dashboardids | No | Return only reports associated with the given dashboard IDs. | |
| extra_params | No | Other native report.get parameters, merged into the request as-is. Parameters: expired (6.0+). Sub-object selects (value 'extend', 'count' or a list of property names): selectUserGroups (6.0+), selectUsers (6.0+). Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call. | |
| searchWildcardsEnabled | No | If true, enable * and ? wildcards in search patterns. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |