> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/itential-platform/6/studio/json-forms/adapters/use-dynamic-dropdown/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Use the dynamic dropdown form element with adapters

> How to configure a JSON Forms dropdown element to fetch data dynamically from an adapter or API in Itential Platform.

JSON Forms in Itential Platform can integrate with APIs or adapters to fetch, manipulate, and display data. This guide covers how to configure adapter calls in JSON Forms.

The communication in this flow is between Itential Platform and the adapter — not a direct call to the external system. The HTTP method used depends on whether the call requires input: calls with no parameters use GET; calls that require parameters or data use POST, even if the adapter's call to the external system is itself a GET.

## Configure the adapter call within the form

#### Add a dropdown element to the canvas

Drag the **Dropdown** element onto the empty canvas.

![](/_fern-files/itential.docs.buildwithfern.com/d1e3ab75b85872e7a4bad54b7f3f1af33f435d09a33eec0a2c9a2bf2453e08b0/docs/assets/images/platform/f08fdeba-b4b2-4a83-bde1-592e088e7ec0.png)

#### Open the Configure dialog

Hover over the three dots in the upper-right corner of the element, then click the gear icon to edit the dropdown. The Configure dialog appears.

![](/_fern-img/2ae4fbb7f3c2646fd50bff4e3cb3c2d97ba4952f387c224bd52f2a7e6c869df7.webp)

#### Select the Dynamic option

Select **Dynamic** to enable adapter-backed data fetching.

![](/_fern-img/aab26f669f7611f52f31e82ae2a4129d8e020ba6876d85e3ce3d8fc75b92ba99.webp)

#### Configure the request

Complete the **Make Request Configuration** fields: **Method**, **Base URL**, **API Route**, and **Request Body**.

![](/_fern-img/e5e25decbac53dfacb82dcd87728c9bded78d283eb2983c013d1f757f5ab5351.webp)

**Method** — Select based on whether the adapter task requires input:

* **POST**: Use when the adapter task requires input parameters.
* **GET**: Use only when the adapter task accepts no input parameters. Confirm this in the adapter's documentation.

Note that the JSON Form always sends a request to the adapter; the adapter itself may then call the external system using a different HTTP method (GET, PUT, etc.) as required.

**Base URL** — Select the adapter you need for the integration. The adapter must already be installed and online in your Itential Platform instance.

**API Route** — Select the route for the adapter task, which follows the structure `/{adapter-task-name}`. API routes for adapter calls are defined in the adapter's `pronghorn.json` file.

**Request Body** — Define the payload for the adapter call. This payload must match the JSON input expected by the adapter task, not the external system. The adapter handles translating this into the format required by the external API.

Include all fields expected by the adapter task, even optional ones. Leave optional fields that are not needed empty. For example, if the adapter task expects three inputs — `id`, `name`, and `body` — where only `id` is required, the Request Body would look like:

```json
{
  "id": "123",
  "name": "",
  "body": {}
}
```

#### Make the API call and review the response

Click **Make API Call**. The output of the call appears in the **Response Body**.

For response filtering and other dropdown capabilities, see [Use the form element dropdown](/itential-platform/studio/json-forms/use-dropdown-elements).

## Key considerations

| Area             | Details                                                                                                                                         |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Base URL**     | Points to the adapter task endpoint within Itential Platform, not the external system. Example: `/adapter-task`                                 |
| **HTTP method**  | Use POST for tasks requiring input. Use GET only when the adapter task has no input requirements.                                               |
| **Request Body** | Must match the format expected by the adapter task. The adapter translates the input into the appropriate format for the external API.          |
| **Permissions**  | Users populating data into the form must have permission to execute the adapter call. This typically requires admin permissions on the adapter. |

> How to configure a JSON Forms dropdown element to fetch data dynamically from an adapter or API in Itential Platform.