> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/v-3.0/get-to-start-automating-web-applications/automated-test-execution/untitled-1/untitled/api-parameterization.md).

# 3.2.1.3.1 API Parameterization

API parameterization is nothing but without interrupt the actual request template we can replace the key values in request.

Below was the syntax for the parameterization

```
Syntax: ${Product Element}
```

Below screen shows the parameterized request template. We created the product elements with name and job.

![](/files/-MbeSPYxtCOs-XCNyckx)

Click on the Default Parameter tab you can find the two buttons, Extract Param with refresh and Extract Params.

![](/files/-MbeSPYya6GilvO_Qzdl)

Click on the **Extract Param button** you get the all parameterized fileds.

![](/files/-MbeSPYzKYbhCtEBmRdJ)

Fill the all the fileds then click on **Save** button and then Click on **Test** button.

![](/files/-MbeSPZ-fOfvfxGJFDsi)

Now you can get response based on the data you are provided in the default parameters.


---

# 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.qatts.com/v-3.0/get-to-start-automating-web-applications/automated-test-execution/untitled-1/untitled/api-parameterization.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.