---
schema_version: "1"
id: 7ad04ffcf802f04a628b81943b7c1d4f219f0fb875d681e07ecd045aac980f66
title: Testing an API Alert
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/test-alert-task.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/test-alert-task
source_site: docs.mulesoft.com
content_type: documentation
content_hash: adf357d953dd523d2ca27ae35f07b29d04f0b46f2eb93b9b715733b20ccc1076
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
---

# Testing an API Alert

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

This procedure describes how to test a request count alert. This procedure requires the following
preparation:

1.  Design an API.

2.  Publish the API to Exchange.

3.  In API Manager, manage the API from Exchange.

4.  Deploy a proxy of the API instance to CloudHub.

5.  Apply the Rate Limiting Policy to the API as follows: Request Count greater than 1 for at least
    1 consecutive minute.

6.  Add the alert described in the topic about how to add an alert.

7.  Call the API.

8.  Recall the API two more times (reload the page). Check that `API calls exceeded` appears if you
    called and recalled the API within the 1 minute period. Any additional page reload operations
    within the 1 minute period have no effect.

9.  Check that users, who you selected for email notification when you added the alert, actually
    receive email notifications.

10. Check that the alert was resolved.

## See Also

- [Add Instance Alerts in API Manager (Mule Gateway)](https://docs.mulesoft.com/api-manager/latest/add-api-alert-task)

- [Create and Publish an API Specification or API Fragment](https://docs.mulesoft.com/design-center/design-create-publish-api-specs)