Learn more about anomalies and how to use them to monitor your API integrations.


A core feature of Bearer is anomaly detection. Anomalies are events caused by an unexpected incident with an API call.

The anomalies overview provides a running list of anomalies grouped by API. You can drill down into an API to view individual anomalies, and see details about each API request just as you would with logs.

Bearer uses Rules to set criteria for detecting an anomaly. By default, each application in Bearer comes with a set of rules that can be used as-is or configured for your use case. You can also create your own rules to detect when an anomaly occurs.

To view existing rules and create your own, select the "Rules" tab from the top navigation.

Here you'll see all rules that are associated with the current application. You can modify rules, toggle their active status, and create new rules.

Creating a new Anomaly Rule

To create a custom Anomaly Rule, select the "Custom Anomaly" button on the Rules screen.

You'll be taken to the New Custom Anomaly page. Here you can define the criteria an API call must meet to trigger the rule.

A rule can be broken down into four parts:

  • General: Information about the rule such as name, description, the APIs it applies to, the type of anomaly it detects, and active status.

  • Detection Conditions: Unique to each rule type, the detection conditions establish the base criteria for a rule to trigger.

  • Call Filtering: Once an anomaly is detected by a rule, you can further narrow the criteria with filtering. Filters allow you to limit rules to certain headers, status codes, HTTP methods, and more.

  • Notification Settings: How would you like to be notified when an anomaly triggers this rule? Your notification settings are application-wide, but each rule can choose to use some, all, or none of the configured notification types.