regexp_get
Read-only
Retrieve global regular expressions for reuse across Zabbix LLD filters and trigger expressions, optionally including their test expressions and filtering by name, ID, or pattern.
Instructions
Retrieve global regular expressions. These named regexp objects are reusable across Zabbix -- referenced in LLD (Low-Level Discovery) rules to filter discovered entities, in trigger expressions, and elsewhere. Each regexp can contain multiple test expressions with different match types (character string included, result is TRUE/FALSE, etc.). Use selectExpressions to include the test expressions.
Input 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: name, regexpid, test_string. Text properties cannot be filtered; use 'search' for them. | |
| output | No | Properties of the regexp object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: regexpid, name. Properties: description (8.0+), name, regexpid, test_string. | |
| search | No | Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description (8.0+), name, test_string. | |
| 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. | |
| regexpids | No | Return only regular expressions with the given IDs. | |
| sortfield | No | Sort by one or more of: regexpid, name (a list 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). | |
| extra_params | No | Other native regexp.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): selectExpressions. 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. |