---
title: "Read one approval run"
method: GET
path: "/api/v1/rest/workflow/instances/{id}"
tags: ["Workflows"]
---

# Read one approval run

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

## Request

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

One run: what it is about, which flow it follows, its status, and every task with who decided what. `detailed` adds the discussion comments. Use this to explain WHY something is stuck.

**Examples**

- Why is that invoice still pending?
  `GET /api/v1/rest/workflow/instances/11111111-2222-4333-8444-555555555555`

## Path parameters

- `id` string, uuid, required

## Query parameters

- `response_format` 'concise' | 'detailed'

## 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)