> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/rest-client-step/options-rest-client/parameters-tab.md).

# Parameters tab

![Parameters tab in REST client](/files/V3dpr1Iv51pNl9rz937X)

Use the **Parameters** tab to define parameter values for **POST**, **PUT**, **DELETE**, and **PATCH** requests. Parameters for the **GET** method should be directly a part of the URL.

The parameters table contains the following columns:

| Column        | Description                                                                |
| ------------- | -------------------------------------------------------------------------- |
| **Parameter** | The field from incoming PDI stream that contains the parameter information |
| **Parameter** | The name of the outgoing PDI field from this step                          |

Use the **Get** button to populate the table with fields from the PDI input stream.

**Note:** The parameters table and the **Get** button are only available when the **HTTP method** in the **General** tab is set to **POST**, **PUT**, **DELETE**, or **PATCH**.


---

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

```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/rest-client-step/options-rest-client/parameters-tab.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.