> This page is for Developer Documentation.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.benchling.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.benchling.com/_mcp/server.

# List ProcedureRunPlanCondition items

GET https://{tenant_name}.benchling.com/api/v3/procedure-run-plan-condition/items

List ProcedureRunPlanCondition items.

Reference: https://docs.benchling.com/docs/api/benchling-api/procedure-run-plan-condition/list

## Authentication

- `Authorization` header (bearer token, required) — Bearer authentication of the form `Bearer <token>`, where token is your auth token.

## Request

### Query parameters

- `createdAt.gt` (string, optional) — Datetime, in RFC 3339 format. Time zone defaults to UTC. Restricts results to those created after the specified time. e.g. > 2017-04-30.
- `createdAt.gte` (string, optional) — Datetime, in RFC 3339 format. Time zone defaults to UTC. Restricts results to those created at or after the specified time. e.g. >= 2017-04-30.
- `createdAt.lt` (string, optional) — Datetime, in RFC 3339 format. Time zone defaults to UTC. Restricts results to those created before the specified time. e.g. \< 2017-04-30.
- `createdAt.lte` (string, optional) — Datetime, in RFC 3339 format. Time zone defaults to UTC. Restricts results to those created at or before the specified time. e.g. \<= 2017-04-30.
- `id.anyOf` (string, optional) — Restricts results to those matching any of the specified IDs. Comma-separated list.
- `modifiedAt.gt` (string, optional) — Datetime, in RFC 3339 format. Time zone defaults to UTC. Restricts results to those modified after the specified time. e.g. > 2017-04-30.
- `modifiedAt.gte` (string, optional) — Datetime, in RFC 3339 format. Time zone defaults to UTC. Restricts results to those modified at or after the specified time. e.g. >= 2017-04-30.
- `modifiedAt.lt` (string, optional) — Datetime, in RFC 3339 format. Time zone defaults to UTC. Restricts results to those modified before the specified time. e.g. \< 2017-04-30.
- `modifiedAt.lte` (string, optional) — Datetime, in RFC 3339 format. Time zone defaults to UTC. Restricts results to those modified at or before the specified time. e.g. \<= 2017-04-30.
- `nextToken` (string, optional) — Token for pagination
- `omit` (string, optional) — Comma-separated list of top-level fields to omit from each returned item. Cannot overlap with returning.
- `pageSize` (integer, optional) — Number of results to return. Defaults to 50, maximum of 100.
- `returning` (string, optional) — Comma-separated list of top-level fields to include in each returned item. Cannot overlap with omit.
- `sort` (enum, optional, default: modifiedAt:desc) — Method by which to order results. Valid sorts are: createdAt (created time, oldest first) and modifiedAt (modified time, oldest first). Use :asc or :desc to specify ascending or descending order. Default is modifiedAt:desc.
  - Allowed values: `createdAt:asc`, `createdAt:desc`, `modifiedAt:asc`, `modifiedAt:desc`

### Headers

- `EARLY-ACCESS` (string, optional) — Set to true to access beta operations via /api/v3.

## Response

### 200

OK

- `items` (list of ProcedureRunPlanCondition, optional)
- `nextToken` (string, optional)

## Errors

### 400 Procedure Run Plan Condition List Request Bad Request Error

Bad Request

- `detail` (GeneralErrorDetail, required, nullable)
- `instance` (string, required)
- `status` (integer, required)
- `title` (string, required, nullable)
- `type` (string, required)
- `invalidId` (string, optional)

### 403 Procedure Run Plan Condition List Request Forbidden Error

Forbidden

- `detail` (GeneralErrorDetail, required, nullable)
- `instance` (string, required)
- `status` (integer, required)
- `title` (string, required, nullable)
- `type` (string, required)
- `invalidId` (string, optional)

### 404 Procedure Run Plan Condition List Request Not Found Error

Not Found

- `detail` (GeneralErrorDetail, required, nullable)
- `instance` (string, required)
- `status` (integer, required)
- `title` (string, required, nullable)
- `type` (string, required)
- `invalidId` (string, optional)

### 429 Procedure Run Plan Condition List Request Too Many Requests Error

Too Many Requests

- `detail` (TooManyRequestsErrorBodyDetail, required, nullable)
- `instance` (string, required)
- `status` (integer, required)
- `title` (string, required, nullable)
- `type` (string, required)
- `invalidId` (string, optional)
- `violated-policies` (list of enum, optional) — The budget policies that rejected the request, in canonical order: `user`, `integration`, then `tenant`.
  - Allowed values: `user`, `integration`, `tenant`

### 500 Procedure Run Plan Condition List Request Internal Server Error

Internal Server Error

- `detail` (InternalServerErrorBodyDetail, required, nullable)
- `instance` (string, required)
- `status` (integer, required)
- `title` (string, required, nullable)
- `type` (string, required)
- `errorId` (string, optional)

## Types

### ProcedureRunPlanCondition

A planned experimental condition within a `ProcedureRunPlan`, representing how a procedure's methods will be configured when the plan is promoted to an actual `ProcedureRun`. Each condition contains pre-filled parameter values (via `MethodParametersPlan`) for the procedure's unit operations, and specifies how many replicates will be run (via `ProcedureRunPlanConditionReplicate`). Scientists use conditions to plan different experimental configurations before execution—for example, testing multiple temperatures or reagent concentrations. The `position` field determines display order within the parent run plan. Upon promotion, each ProcedureRunPlanCondition becomes a `ProcedureRunCondition` in the resulting experiment. Also known as an "experiment condition" in the Benchling UI's experiment planning workflow.

- `__typename` (string, optional)
- `createdAt` (string, optional)
- `description` (string, optional) — The user-defined description of the condition.
- `id` (string, optional)
- `methodParametersPlan` (MethodParametersPlan, optional, nullable) — Method plan containing parameter values for this condition's unit operation. If this value is null upon promotion to a procedure run, default values from the procedure will be used.
- `modifiedAt` (string, optional)
- `name` (string, optional) — The user-defined name of the condition.
- `position` (integer, optional) — The display order of the condition within the run.
- `procedureRunPlan` (ProcedureRunPlanRef, optional) — The ProcedureRunPlan that this condition is a part of.
- `replicates` (list of ProcedureRunPlanConditionReplicate, optional) — Replicate information for this condition.
- `templateMethodVersion` (ProcedureMethodDefinitionVersionRef, optional) — The procedure method definition version (PMDV) this condition belongs to.

### GeneralErrorDetail

### TooManyRequestsErrorBodyDetail

### InternalServerErrorBodyDetail

### MethodParametersPlan

Contains the planned parameter values for a single unit operation (method) within a `ProcedureRunPlanCondition`. Links to a `ProcedureMethodDefinitionVersion` via `templateMethodVersion` to identify which method these values apply to. Parameter values are organized by category: `dataParameterValues` for data fields like numbers or text, `materialInputValues` for sample or reagent inputs, and `equipmentValues` for equipment assignments. When the parent `ProcedureRunPlan` is promoted to a `ProcedureRun`, these planned values become the starting values in the resulting `ProcedureMethodExecutionInstance`.

- `__typename` (string, optional)
- `dataParameterValues` (list of DataParameterValuePlan, optional) — Planned values for data parameters keyed by parameter identifiers.
- `equipmentValues` (list of EquipmentValuePlan, optional) — Planned values for equipment keyed by equipment identifiers.
- `materialInputValues` (list of MaterialInputValuePlan, optional) — Planned values for material inputs keyed by input identifiers.

### ProcedureRunPlanRef

- `__typename` (string, optional)
- `id` (string, optional)

### ProcedureRunPlanConditionReplicate

Represents a planned replicate within a `ProcedureRunPlanCondition`. Scientists often run the same experimental condition multiple times to obtain statistically significant results—each repetition is a replicate. The `replicateNumber` provides a one-indexed identifier (e.g., replicate 1, 2, 3). The `sourcePmeiIds` field supports unit operation linking by storing source `ProcedureMethodExecutionInstance` IDs from other procedure runs. Upon promotion of the parent `ProcedureRunPlan`, each ProcedureRunPlanConditionReplicate becomes a `ProcedureRunConditionReplicate` in the resulting procedure run.

- `__typename` (string, optional)
- `procedureRunPlanCondition` (ProcedureRunPlanConditionRef, optional) — The ProcedureRunPlanCondition that this replicate belongs to.
- `replicateNumber` (integer, optional) — The replicate number.
- `sourcePmeiIds` (list of string, optional) — Source PMEI IDs for this replicate. Support unit operation linking to future-pmeis when executing the draft procedure run.

### ProcedureMethodDefinitionVersionRef

- `__typename` (string, optional)
- `id` (string, optional)

### DataParameterValuePlan

A pre-filled value for a data parameter within a `MethodParametersPlan`. The `parameterId` references the `ProcedureParameterVersion` this value applies to. The `value` field contains the planned data in JSON format, which may be a number, string, or structured value depending on the parameter's data type configuration. Used during experiment planning to specify default values that will populate the parameter when the procedure run is created.

- `__typename` (string, optional)
- `parameterId` (string, optional)
- `value` (map from string to any, optional)

### EquipmentValuePlan

A pre-filled value for an equipment parameter within a `MethodParametersPlan`. The `equipmentId` references the `ProcedureParameterVersion` for the equipment parameter this value applies to. The `value` field contains the planned equipment assignment in JSON format, typically specifying which piece of lab equipment will be used. Used during experiment planning to pre-assign instruments or devices that will be used when the procedure run is executed.

- `__typename` (string, optional)
- `equipmentId` (string, optional)
- `value` (map from string to any, optional)

### MaterialInputValuePlan

A pre-filled value for a material input within a `MethodParametersPlan`. The `materialInputId` references the `ProcedureParameterVersion` for the material input this value applies to. The `value` field contains the planned material specification in JSON format, typically including sample references and quantities. Used during experiment planning to pre-assign samples, reagents, or other materials that will be used when the procedure run is executed.

- `__typename` (string, optional)
- `materialInputId` (string, optional)
- `value` (map from string to any, optional)

### ProcedureRunPlanConditionRef

- `__typename` (string, optional)
- `id` (string, optional)

## Examples

**Response**

```json
{
  "items": [
    {
      "__typename": "__typename",
      "createdAt": "createdAt",
      "description": "description",
      "id": "id",
      "modifiedAt": "modifiedAt",
      "name": "name",
      "position": 1,
      "replicates": [
        {}
      ]
    }
  ],
  "nextToken": "nextToken"
}
```

**SDK Code**

```python
import requests

url = "https://{tenant_name}.benchling.com/api/v3/procedure-run-plan-condition/items"

headers = {"Authorization": "Bearer <token>"}

response = requests.get(url, headers=headers)

print(response.json())
```

```javascript
const url = 'https://{tenant_name}.benchling.com/api/v3/procedure-run-plan-condition/items';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}
```