---
title: "Prose Status"
method: GET
path: "/repos/{repo_id}/prose/status"
tags: ["repos"]
---

# Prose Status

`GET /repos/{repo_id}/prose/status`

Prose-job lifecycle for one snapshot -- never wiki availability.

``snapshot`` pins the answer the same way the estimate and generate bodies
do. Without it this endpoint would keep reporting the latest snapshot's job
while the client polls a job it just started on a different one, which would
make the targeting above pointless the moment progress is rendered.

## Path parameters

- `repo_id` string, required

## Query parameters

- `snapshot` string, nullable

## Response `200`

Successful Response

- ProseStatusResponse
  - `prose_job_id` string, nullable, required
  - `prose_status` string, nullable, required
  - `phase` string, nullable
  - `trigger` string, nullable
  - `wiki_available` boolean, required
  - `wiki_format` string, nullable, required
  - `eligible_total` integer, nullable
  - `eligible_missing_prose` integer, nullable
  - `selected_count` integer, nullable
  - `selected_page_ids` string[], nullable
  - `completed_count` integer, nullable
  - `failed_count` integer, nullable
  - `estimated_cost_cents` integer, nullable
  - `actual_cost_cents` integer, nullable
  - `error` string, nullable

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/repowise/apis/repowise-hosted-api.md) · [All operations](https://skmtc.dev/repowise/apis/repowise-hosted-api/llms.txt) · [OpenAPI document](https://skmtc.dev/repowise/apis/repowise-hosted-api/revisions/6bb9d0da77e3?raw)