---
title: "Get Clarity Process Snapshot"
method: GET
path: "/v2/clarity-v2/processes/{process_id}/snapshots/{kind}/{snapshot_id}"
tags: ["ClarityV2"]
---

# Get Clarity Process Snapshot

`GET /v2/clarity-v2/processes/{process_id}/snapshots/{kind}/{snapshot_id}`

Fetch the full payload for a Clarity v2 process snapshot of either kind.

## Path parameters

- `process_id` string, uuid, required
- `kind` 'current_process' | 'transformation_proposal', required
- `snapshot_id` string, uuid, required

## Response `200`

Default Response

- object
  - `snapshot` union, required
    - object
      - `id` string, uuid, required — Snapshot id
      - `process_id` string, uuid, required — Parent clarity_process id
      - `source_snapshot_id` 'null', nullable, required
      - `parent_id` string, uuid, nullable, required — Parent snapshot this row forked from, if any
      - `created_at` string, required — ISO 8601 creation timestamp
      - `updated_at` string, required — ISO 8601 last-update timestamp
      - `status` 'live' | 'historic' | 'draft' | 'generating', required — Versioning state. Only one 'live' row per process at a time; drafts may be edited or generating before promotion.
      - `creator_type` 'human' | 'ai', required — Whether this row was created by a user edit ('human') or an AI pipeline run ('ai').
      - `user_id` string, uuid, nullable, required — Creator user id (the human who edited or triggered the run).
      - `sandbox_id` string, nullable, required — E2B sandbox id that produced AI rows; null for user edits.
      - `last_session_id` string, nullable, required — Claude SDK session id for artifact-chat follow-up reuse.
      - `kind` 'current_process', required
      - `data` object, required — Opaque BPMN payload describing the captured current process.
        - `version` integer, required — Schema version for the current process data payload. Increment on breaking changes to the data shape so consumers can branch on the version field.
        - `steps` union[], required — Ordered steps describing how the process works today, extracted from captures. Array position is the canonical order; BPMN topology is encoded by each step's targetSteps[] edges.
          - union
            - object
              - …
            - object
              - …
            - object
              - …
        - `swot` object, nullable — SWOT analysis produced by the swot-analysis postprocessing agent. `undefined` = agent has not yet run; `null` = agent ran and produced no analysis.
          - `strengths` string[], required — Internal advantages of the current process — capabilities, resources, or design choices that work in its favour today. Phrase each as a short, evidence-backed statement. Example: "Bartenders know regulars by name, which keeps service personal during peak hours."
          - `weaknesses` string[], required — Internal limitations of the current process — gaps, inefficiencies, or fragile assumptions visible in how it runs today. Phrase each as a short, evidence-backed statement. Example: "Manual pour times balloon during rushes because there is only one tap."
          - `opportunities` string[], required — External openings the current process could exploit — adjacent automations, scale effects, or unmet needs surfaced by the captures. Example: "POS data could feed dynamic pricing for slow hours."
          - `threats` string[], required — External risks that could degrade the current process — regulatory, operational, technological, or human factors visible in the captures. Example: "New ID-check legislation will require staff to interrupt every order."
        - `summary` string, nullable — One short paragraph (3-5 sentences) describing the captured process at a glance. Surfaced at the top of the current-process tab so reviewers can orient themselves before scanning the steps. Example: "Customers order beer at the bar; the bartender greets them, picks an option matching their preference, pours and garnishes the glass, then rings the order through the POS before serving."
    - object
      - `id` string, uuid, required — Snapshot id
      - `process_id` string, uuid, required — Parent clarity_process id
      - `source_snapshot_id` string, uuid, required
      - `parent_id` string, uuid, nullable, required — Parent snapshot this row forked from, if any
      - `created_at` string, required — ISO 8601 creation timestamp
      - `updated_at` string, required — ISO 8601 last-update timestamp
      - `status` 'live' | 'historic' | 'draft' | 'generating', required — Versioning state. Only one 'live' row per process at a time; drafts may be edited or generating before promotion.
      - `creator_type` 'human' | 'ai', required — Whether this row was created by a user edit ('human') or an AI pipeline run ('ai').
      - `user_id` string, uuid, nullable, required — Creator user id (the human who edited or triggered the run).
      - `sandbox_id` string, nullable, required — E2B sandbox id that produced AI rows; null for user edits.
      - `last_session_id` string, nullable, required — Claude SDK session id for artifact-chat follow-up reuse.
      - `kind` 'transformation_proposal', required
      - `data` object, required — Opaque BPMN payload for the proposed transformed process.
        - `version` integer, required — Schema version for the transformation proposal data payload. Increment on breaking changes to the data shape so consumers can branch on the version field.
        - `steps` union[], required — Ordered steps describing the proposed redesigned process. Same shape as the current process steps; BPMN topology is encoded by each step's targetSteps[] edges.
          - union
            - object
              - …
            - object
              - …
            - object
              - …
        - `summary` string, nullable — One short paragraph (3-5 sentences) describing the proposed transformed process at a glance. Surfaced at the top of the transformation-proposal tab so reviewers can orient themselves before scanning the steps. Example: "Customers self-order on a tablet at the bar; a smart tap auto-pours the chosen beer into a labelled glass, which the customer collects from the pickup counter once payment clears."
        - `projectedImpact` string, nullable — Answer-first, MECE-structured business case. 4-8 sentences of prose + one markdown assumptions table. Null when team context is insufficient to produce any quantitative or qualitative assessment.

## Other responses

- `400` — Default Response
- `401` — Default Response
- `403` — Default Response
- `404` — Default Response
- `500` — Default Response

---

[API](https://skmtc.net/duvo/apis/duvo-public-api.md) · [All operations](https://skmtc.net/duvo/apis/duvo-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/duvo/duvo-public-api/revisions/dafcf3d868a9/schema)