# JSON Matcher

JSON matching will match exactly the JSON that is entered into the editor. The order of the objects is irrelevant, but the JSON document as a whole should evaluate to exactly what is typed into the editor.

Do not confuse this with the EXACT matcher which looks for exact string content. The JSON matcher looks for exact JSON content and doesn't care about order, only structure and values.

### JSON Matching example:

| **Matcher value**                                             | **Positive match payload**           | **Non match payload**                                         |
| ------------------------------------------------------------- | ------------------------------------ | ------------------------------------------------------------- |
| <p>{</p><p>"name": "John",</p><p>"surname": "Doe"</p><p>}</p> | { "surname": "Doe" , "name": "John"} | <p>{</p><p>"name": "Jane",</p><p>"surname": "Doe"</p><p>}</p> |


---

# Agent Instructions: 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:

```
GET https://docs.cloud.hoverfly.io/create-simulations/configuring-request-matchers/json-request-matchers-on-the-body/json-matcher.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.