---
schema_version: "1"
id: f347656764c794c3eed5a285009382327dc05be7a40ebc20ab2fe36d31bbfc1b
title: API Functional Monitoring with the Blackbox Automated Testing (BAT) CLI
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-functional-monitoring/bat-top.md
canonical_url: https://docs.mulesoft.com/api-functional-monitoring/bat-top
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 42d77e46e8455293df83cb239cf1effe4b46d0b679e4fa941cb268347775bee1
description: MuleSoft Documentation Site
latest: true
---
---
product: API Functional Monitoring
---

# API Functional Monitoring with the Blackbox Automated Testing (BAT) CLI

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

You can use API Functional Monitoring to run a test or suite of tests on an API. API Functional
Monitoring is based on Blackbox Automated Testing (BAT).

Using API Functional Monitoring, you can automate testing and get test reports. You can test before
pushing code into your repository and before deploying to production. Tests can verify API
functionality and validate results the API generates. You can monitor APIs at each stage of the
software development life cycle and in production.

The prerequisites for testing and scheduling are:

- One or more deployed APIs

- Installation of BAT.

- A directory that contains a test suite.

- At least one test file in that directory.

  You write tests in Behavior Driven Development (BDD) syntax using a code or text editor, such as
  IntelliJ. Test files must use the `.dwl` extension for processing by DataWeave.

An additional prerequisite, this one for monitoring scheduled tests in the cloud, is an account on
Anypoint Platform.

## See Also

- [Install BAT](https://docs.mulesoft.com/api-functional-monitoring/bat-install-task)

- [BDD Test Writing Language Reference](https://docs.mulesoft.com/api-functional-monitoring/bat-bdd-reference)