---
title: "Read one flow’s definition"
method: GET
path: "/api/v1/rest/workflow/flows/{id}"
tags: ["Workflows"]
---

# Read one flow’s definition

`GET /api/v1/rest/workflow/flows/{id}`

## Request

- Base URL: `https://api.custodo.ai`
- URL: `https://api.custodo.ai/api/v1/rest/workflow/flows/{id}`
- Auth: HTTP bearer

The authored definition of one flow — its stages (each with its `id`), approvers, custom fields (each with its `key`) and (Premium) automated steps — exactly as the builder reads it, un-resolved table sources included. Read it before workflow_update_flow, which needs those ids and keys; to start a run use workflow_start.

**Examples**

- What does the invoice approval flow actually do?
  `GET /api/v1/rest/workflow/flows/33333333-4444-4555-8666-777777777777`

## Path parameters

- `id` string, uuid, required

## Headers

- `X-Tenant-Id` string, uuid

## Response `200`

Done. `data` is the tool’s own answer.

- RestResult
  - `ok` true, required
  - `data` unknown, required

## Other responses

- `400`: The arguments did not validate: `error.message` names the field, what it expects and what arrived.
- `401`: No API key, or one that is malformed, unknown, revoked or expired.
- `403`: The call never ran: the module is off for this organisation, the credential lacks the permission or the module, the tier does not cover it, or the tool is destructive and the key was not minted for that.
- `404`: Nothing with that id in this organisation.
- `422`: The tool ran and refused, in a sentence of its own (`TOOL_REFUSED`): the message says what to change. Retrying the same call will not help.
- `429`: The API key has spent its minute, or its day. Every request a key makes counts. See `Retry-After`.

---

[API](https://skmtc.dev/custodo/apis/custodo-integrazioni.md) · [All operations](https://skmtc.dev/custodo/apis/custodo-integrazioni/llms.txt) · [OpenAPI document](https://skmtc.dev/custodo/apis/custodo-integrazioni/revisions/16d336d3ec2a?raw)