---
title: "Follow work that answered 202"
method: GET
path: "/client/operations/{id}"
tags: ["Apps"]
---

# Follow work that answered 202

`GET /client/operations/{id}`

## Request

- Base URL: `https://api.roar-ai.com`
- URL: `https://api.roar-ai.com/client/operations/{id}`
- Auth: HTTP bearer

The read-back for every route here that answers 202 (`app-insight`, `autofix`). Poll it every couple of seconds until `status` is `done` — `result` is then the body the route would have answered with — or `failed`, where `error` carries the status and message it would have refused with. A `running` operation older than the platform restart window reads as `failed` with a message saying so. Rows are kept seven days. Readable by a session, or by a key holding the scope the starting route required; any other company's id is a 404.

## Path parameters

- `id` string, uuid, required

## Response `200`

The operation

- OperationView
  - `id` string, uuid, required
  - `kind` string, required: What ran: `autofix` or `app-insight` on this surface
  - `status` 'running' | 'done' | 'failed', required
  - `result` unknown, required
  - `error` object, nullable, required: Set when `failed`: the status and message the route would have refused with
    - `status` integer, required
    - `message` string, required
  - `startedAt` string, date-time, required
  - `finishedAt` string, date-time, nullable, required

## Other responses

- `403`: Key lacks the scope the starting route required
- `404`: No such operation for you

---

[API](https://skmtc.dev/roar-ai/apis/roar-ai-api.md) · [All operations](https://skmtc.dev/roar-ai/apis/roar-ai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/roar-ai/apis/roar-ai-api/revisions/37e4d0d5a7fe?raw)