# Parameterization

If you love to create and manage all your manual requests in one place then parameterization is for you!

## Contents

* [Parameterization](#parameterization)
  * [Get started with Parameterization](#get-started-with-parameterization)
  * [Related Content](#related-content)

***

### Get started with Parameterization

To begin with, navigate within the Manual Asset for which you intend to create parameterized requests.

On the right panel, you'll find a toggle named "Parameterized API" as shown below.

![Parameterization](/files/vKc0R2j93FixqbHVVReU)

In the above image, you'll find a couple of input fields for parameterization. let's understand that.

* **Headers Column**: You can parameterize the Header's value.
* **Query Parameter Column**: You can parameterize Query Param's value.
* **Path Parameter Column**: You can parameterize the Path Param's value.

> The request and response body will automatically be included as a standard part of the parameterized file.

> Not all fields need to be filled in. If you choose not to provide values for certain fields, that's perfectly fine – you can simply remove them.

Once fields are filled with data. click on the "Update" button to update the asset.

The next step is to download the parameterized file and fill in the data in the file.

![DownloadTemplate](/files/lCU3hVFneInVRpn8meRi)

Once the template is downloaded, You can open the file and start filling in the data as shown below.

![ExcelFile](/files/JTAPT98WUyv7nUN5i4qN)

Let's understand all the fields shown in the Excel file.

* **TestCase**: This is nothing but the Request and Response name which we provide under the Info & headers tab.
* **ResponseBody**: This will be the default field for parameterized files as the Response body is mandatory for all requests.
* **StatusCode**: This will be the default field for parameterized files as a Status code is also necessary for all requests.
* **Delay**: Delay you can provide either 0 or any value in ms.
* **content-type and id**: The fields we provided when downloading the template may differ depending on the input we provide for the parameterized file.

Now let's fill in the data and Save the Excel file.

![ExcelData](/files/pwAd8ZMqZJThe19JCOmN)

Once the file is saved, It's time to Upload the template and Import those data as Requests inside the Manual Asset.

To achieve that click on the "Upload Template" button to select the file and Upload the saved Excel file.

![UploadTemplate](/files/aV4mjw6bQRfVp6XR8BEB)

Once the template is uploaded, you'll see data is imported as Requests inside that Asset.

![UploadResult](/files/t5CjYACILtt6SGCOA4VQ)

Now you can play around with those requests, you can edit delete, or add new requests as well.

That's Parameterization for you!!!

***

### Related Content

* [Global Variable](/service-virtualization/advanced-features/global-variable.md)
* [Strict Mode](/service-virtualization/advanced-features/strict-mode.md)


---

# 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.qyrus.com/service-virtualization/advanced-features/parameterization.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.