> 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/generic/xml-and-json-operations/get-tag-value/data-path-builder.md).

# Data Path Builder

The Data Path Builder helps you to generate the required key path for the Get Key Value and Get Tag Value actions. It allows you to navigate through JSON or XML data, select the required node or parameter, and automatically generate the corresponding path.

Depending on the input provided, the Data Path Builder supports the following functionalities:

<details>

<summary><strong>Generating a Path from the Existing Input Value</strong></summary>

Use this functionality when the JSON or XML body is already available in the Input Value column.

To generate a key path, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Test Case** page.
3. Select **Generic** 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-webservice-test-steps).
{% endhint %}

4. Select the **Get Key Value** or **Get Tag Value** action.
5. In the **Input Value** column, enter the JSON or XML body.
6. Select the **Data path builder** icon. The **Data path builder** dialog opens.

{% hint style="info" %}
**Note**: The **Source Data** section displays the JSON or XML body entered in the **Input Value**.
{% endhint %}

7. Select **Beautify** to format the data, if required.
8. From the **Data structure** section, select the required node or parameter.
9. The generated path appears in the **Data path** text box.
10. Select **Add**.

The **Data path builder** adds the generated key path to the **Input Value** column in the required syntax format.

</details>

<details>

<summary><strong>Generating a Path by Providing Source Data in the Data Path Builder</strong></summary>

Use this functionality when the JSON or XML body is directly provided in the Source Data

To generate a key path, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Test Case** page.
3. Select **Generic** 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-webservice-test-steps).
{% endhint %}

4. Select the **Get Key Value** or **Get Tag Value** action.
5. Select the **Data path builder** icon. The **Data path builder** dialog opens.
6. In the **Source data** section, enter the JSON or XML body.
7. Select **Beautify** to format the data, if required.
8. From the **Data structure** section, select the required node or parameter.
9. The generated path appears in the **Data path** text box.
10. Select **Add**.

The **Data path builder** adds the JSON or XML body along with the generated key path to the Input Value column in the required syntax format.

</details>

<details>

<summary><strong>Generating a Path Using a Variable</strong></summary>

Use this functionality when the JSON or XML body is stored in a variable.

To generate a key path, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Test Case** page.
3. Select **Generic** 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-webservice-test-steps).
{% endhint %}

4. Select the **Get Key Value** or **Get Tag Value** action.
5. In the **Input Value** column, enter the variable that contains the JSON or XML body.
6. Select the **Data path builder** icon. The **Data path builder** dialog opens.
7. In the **Source data** section, enter the JSON or XML body.
8. Select **Beautify** to format the data, if required.
9. From the **Data structure** section, select the required node or parameter.
10. The generated path appears in the **Data path** text box.
11. Select **Add**.

The **Data path builder** adds the generated key path to the Input Value column while retaining the variable reference.

{% hint style="info" %}
**Note**: This functionality works only during execution because the variable value is available at runtime.
{% endhint %}

</details>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FIPFMRzlgw2xdoCNFMkxL%2Fimage.png?alt=media&amp;token=a99fa0ae-489b-4bc9-acfc-75e9ef275fe0" alt=""><figcaption></figcaption></figure>


---

# 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/generic/xml-and-json-operations/get-tag-value/data-path-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.
