# Extractions - Set Parameters

Use the **Extractions - Set Parameters** section of the request to extract values from the responses. These extracted values can be use in any of the following requests or to assert and verify your success criteria.

![The request Extractions - Set Parameters section](/files/-Ml9SIw6apzelQsYPuvq)

## Extraction Types

### Assign

Use this to assign any combination of existing parameter or response values to another parameter

![](/files/-Ml4wxHOLpnEkj6LomQZ)

### JSONPath

Use this extractor to extract values from JSON responses. JSONPath is a query language for JSON objects, much like XPath for XMLs.

![](/files/-Ml4xTxazsrtLhgsH-Pj)

You can easily find a relevant JSON Path expression by using our JSON Path Finder feature. To use it, just run your test flow, go to the Response body section, click on JSONPATH and copy the JSON Path expression you need.

![](/files/-MZHL8kEPdzyenDocHew)

![Copying a JSON Path expression from the finder](/files/-MZHLLZDiwG--47lse6Q)

Also find helpful JSON Path expressions [here](https://goessner.net/articles/JsonPath/index.html#e2).

### Clojure

Use this extractor to extract values from Clojure (EDN content type) responses. You need to enter JSONPath Query, Clojure queried as JSON.

![](/files/-Ml4xqLtYAdC5jlqkRlN)

### jQuery

Use this extractor to extract values from HTML or XML responses. jQuery extraction syntax is very similar to XPath and may be very useful to extract values from HTML pages (such as [security tokens](https://portswigger.net/web-security/csrf/tokens)).

![](/files/-Ml4y8IEMq0TepNcmdjG)

### RegExp

Use this extractor to extract values from any type of response using RegExp. The first value captured by the regex (in parentheses) will be set as the parameter's value. You can test your regex expressions using this useful online tool - [link](https://regex101.com).

![](/files/-Ml4yOojCAMr1gVPkRMa)

### Header

Use this extractor to extract values from any of the response headers.

![](/files/-Ml4ygdP5i_ge2e3i0Z0)

## Suggestions

In many cases Loadmill users use the same or similar extractions and [assertions](https://docs.loadmill.com/api-testing/test-suite-editor/assertions). We've implemented the Suggestions feature that allows team admins to configure a repository of extractions and assertions within **Settings - Suggestions**.

Then, each user can add the extractions from the repository by clicking **+ SUGGESTIONS**.

![](/files/-Ml4ysn3rQNF_J71IsXR)

By default, there are a few common extraction and assertion examples in the repository. Team admins can also navigate to the Suggestions Settings directly from within the suggestion dialog window.

![](/files/-M_G7232wBDcWdKiNqM3)

## Autocomplete

{% hint style="info" %}
:man\_mage: Use the autocomplete option to see a list of existing parameters. To see it, press Shift + Cmd (Ctrl for Windows) + Space. See how it works below.
{% endhint %}

![](/files/1vy5dZarpZ7rgqGoKVlR)


---

# 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.loadmill.com/test-editor/set-parameters-extractions.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.