> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/apis/assertion/jsonpath-match/assertion-expression-builder.md).

# Assertion Expression Builder

The Assertion expression builder simplifies the process of creating JSONPath expressions for API assertions. It allows you to navigate through the JSON body, select the required node or parameter, and generate the JSONPath expression, expected value, and match type.

To create JSON expression through assertion expression builder, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Test Case** page.
3. Select Test Case and create an API Test Step Group.
4. Select **@Assertion** from **Elements** column.

{% hint style="info" %}
**Note**: To know more about test step creation, [click here](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/creating-apis-test-case.md#creating-test-steps).
{% endhint %}

5. Select the **JSONPath** action.
6. Select the **Open assertion expression builder** icon. The **Assertion expression builder** dialog opens.
7. In the **Response Body** section, enter the JSON response body manually.
8. From **Select expected result node**, select a node to generate the JSON expression.
9. From the **Match Type** dropdown, select the required match type, such as **Equal**, **Not Equal**, or **Regex**.
10. From **Expected Result**, select the value or node to fetch from the JSON response. The **Expression** is generated based on the selected **Expected Result**.
11. Select **Add**.

{% hint style="info" %}
**Note**: To create a conditional expression, use a filter expression and enter the required value manually in the **Input Value** column.
{% endhint %}

The Assertion expression builder adds the generated expected result and expression to the Input Value column in the required syntax format.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FMblcplsXDAcHQdsugXri%2Funknown.png?alt=media&amp;token=f60c4e1c-4a5b-4634-99cd-9d395289f78e" alt="" width="563">


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/apis/assertion/jsonpath-match/assertion-expression-builder.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.