# Input Parameters JSON Format

> When using the `-i` or `--input_path` parameter to pass input arguments to your process or test set, you need to provide a JSON file with the following structure:

## Input Parameters JSON Format

When using the `-i` or `--input_path` parameter to pass input arguments to your process or test set, you need to provide a JSON file with the following structure:

```json
[
  {
    "name": "first",
    "type": "System.String, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
    "value": "\"parameterValue1\""
  },
  {
    "name": "second",
    "type": "System.Int32, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
    "value": "12"
  },
  {
    "name": "third",
    "type": "System.Boolean, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
    "value": "true"
  }
]
```

Each parameter object must contain:

- **name** - The parameter name as defined in your workflow
- **type** - The fully qualified .NET type name including assembly information
- **value** - The parameter value

### Understanding the type field

The `type` field specifies the .NET data type of the parameter. This is crucial for the CLI to correctly interpret and pass the value to your workflow. The type must be the fully qualified assembly name, which includes:

- The type name (e.g., `System.String`, `System.Int32`, `System.Boolean`)
- The assembly where the type is defined
- Assembly metadata (version, culture, public key token)

Common examples:
- **String**: `System.String, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e`
- **Integer**: `System.Int32, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e`
- **Boolean**: `System.Boolean, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e`

:::tip
To obtain the correct type information for your parameters, you can inspect the workflow's `.xaml` file or use reflection tools to get the fully qualified type name from your .NET assemblies.
:::