Skip to content

docs(cloud): mark /api/history_v2 as deprecated, prefer /api/jobs#897

Open
MillerMedia wants to merge 1 commit intomainfrom
mattmiller/deprecate-history-v2-docs
Open

docs(cloud): mark /api/history_v2 as deprecated, prefer /api/jobs#897
MillerMedia wants to merge 1 commit intomainfrom
mattmiller/deprecate-history-v2-docs

Conversation

@MillerMedia
Copy link
Copy Markdown
Contributor

Summary

  • Marks /api/history_v2 and /api/history_v2/{prompt_id} as deprecated: true in openapi-cloud.yaml so Mintlify renders a deprecation banner, with descriptions pointing at /api/jobs and /api/jobs/{job_id} as replacements.
  • Updates the complete-example snippets (EN + ZH) to fetch outputs via /api/jobs/${prompt_id} — the prompt_id returned by /api/prompt is literally the job UUID (services/ingest/server/implementation/prompt.go:392), and JobDetailResponse.outputs has the same shape the snippets were already reading.
  • Docs-repo-only. No runtime spec changes in the cloud repo (services/ingest/openapi.yaml untouched) — full deprecation/removal is tracked for a future Linear ticket under Core ↔ Cloud Catchup, following the BE-120/121 pattern.

Notes for review

  • Wording intentionally leaves the removal date open ("will be removed in a future release; no removal date set") since there's no timeline yet.
  • Deprecation-link syntax uses the Mintlify OpenAPI anchor format ([\/api/jobs`](#tag/job/GET/api/jobs)`); worth a quick Mintlify preview check to confirm it renders as a link.

Test plan

  • Mintlify preview renders a deprecation banner on /api/history_v2 and /api/history_v2/{prompt_id}
  • Anchor links in the deprecation notes resolve to the /api/jobs and /api/jobs/{job_id} operations
  • Complete-example snippet still compiles/runs end-to-end against cloud (prompt_id/api/jobs/{prompt_id} returns outputs)
  • Chinese mirror (snippets/zh/cloud/complete-example.mdx) renders consistently with the English version

🤖 Generated with Claude Code

Add `deprecated: true` on both /api/history_v2 operations in the
OpenAPI spec so Mintlify renders a deprecation banner, and point
readers at /api/jobs and /api/jobs/{job_id} as replacements. The
prompt_id returned by /api/prompt is the same UUID as job_id, so
client code can swap the path without any other changes.

Update the complete-example snippets (EN + ZH) to fetch outputs via
/api/jobs/${prompt_id} instead of /api/history_v2/${prompt_id}. The
JobDetailResponse schema already exposes the same `outputs` field
the snippets read.

No runtime spec changes in the cloud repo — deprecation is docs-only
until a Linear ticket is filed for the full removal pass.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@mintlify
Copy link
Copy Markdown
Contributor

mintlify bot commented Apr 9, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
comfy 🟢 Ready View Preview Apr 9, 2026, 3:06 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant