> For the complete documentation index, see [llms.txt](https://docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akto.io/api-protection/concepts/ignore-events-at-rule-level.md).

# Configure Ignored Events Per Rule

**Ignore Events at Rule Level**

You can configure threat rules to skip evaluation for specific APIs by adding an `ignore:` block. When an API matches the conditions in the `ignore:` block, the rule will not be evaluated further for that particular API.

**How to configure**

Add an `ignore:` block to any threat rule following the similar syntax as `filters:` block.

**Syntax Reference:** For detailed syntax on how to define API selection filters, see [API Selection Filters](https://docs.akto.io/test-editor/concepts/test-yaml-syntax-detailed/api-selection-filters).

**Example: Ignoring Specific Endpoints**

This example shows how to ignore evaluation for APIs that contain `/health` or `/status` in their URL:

```yaml
id: ExampleThreatRule
ignore:
  url:
    contains_either:
      - "/health"
      - "/status"

filter:
  # Your threat detection filters here

info:
  name: "Example Threat Rule"
  description: "Detects potential threats"
  severity: HIGH
```

When this rule is processed, any API with `/health` or `/status` in the URL will be skipped and the rule will not be evaluated for those APIs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akto.io/api-protection/concepts/ignore-events-at-rule-level.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.