> For the complete documentation index, see [llms.txt](https://docs.cloud.hoverfly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud.hoverfly.io/create-simulations/configuring-request-matchers.md).

# Configuring Request Matchers

In order to select a response to return from the sets of request/response pairs that you configure on an API simulation, Hoverfly evaluates the request matchers to find the one that matches the incoming request.

The request matchers are rules that specify what combination of request method, destination, path, headers, query parameters and body content should evaluate positively so that the corresponding response is returned.

Method request matchers can be set to match on ANY HTTP Verb, or a specified HTTP Verb. Destination, path, headers and query parameter matchers can be exact strings, strings containing globs (wildcards), or regular expression patterns.

All of these matchers can be combined so that your simulation can match on specific combinations of method, destination, path, headers, query parameter and body (payload) content.


---

# 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.cloud.hoverfly.io/create-simulations/configuring-request-matchers.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.