---
title: "Get ProcedureFlowchart by ID"
method: GET
path: "/api/v3/procedure-flowchart/{procedure_flowchart_id}"
tags: ["Procedure Flowchart"]
---

# Get ProcedureFlowchart by ID

`GET /api/v3/procedure-flowchart/{procedure_flowchart_id}`

## Request

- Base URL: `https://{tenant_name}.benchling.com`
- URL: `https://{tenant_name}.benchling.com/api/v3/procedure-flowchart/{procedure_flowchart_id}`
- Auth: HTTP bearer

Get a single ProcedureFlowchart by ID.

## Path parameters

- `procedure_flowchart_id` string, required

## Query parameters

- `returning` string[]
- `omit` string[]

## Headers

- `EARLY-ACCESS` string

## Response `200`

OK

- ProcedureFlowchart: Contains the legacy flowchart configuration for a Procedure or TemplateCollection. A ProcedureFlowchart tracks both the latest working version and the published version that is used when creating procedure runs. The parent relationship (see `parent`) connects this flowchart to either a `Procedure` or `TemplateCollection`. Note that this model will be deprecated soon, in favor of `WorkflowFlowchartConfig`. ## Product mapping - In the Benchling product experience, this corresponds to the **legacy procedure template flowchart container**. - For Workflows-backed procedures, prefer `ProcedureFlowchartConfigVersion` when you need the graph that users see in modern planning/execution experiences.
  - `__typename` string
  - `archiveReason` string, nullable
  - `archived` boolean
  - `createdAt` string, datetime
  - `id` string
  - `modifiedAt` string, datetime
  - `parent` ProcedureFlowchartParentRef
    - `__typename` string
    - `id` string, api_id

## Other responses

- `400`: Bad Request
- `403`: Forbidden
- `404`: Not Found
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/benchling/apis/benchling-api.md) - [All operations](https://skmtc.dev/benchling/apis/benchling-api/llms.txt) - [OpenAPI document](https://skmtc.dev/benchling/apis/benchling-api/revisions/c9f087b98b8b?raw)