List bundles, and the folders that look like bundles but are not valid.
const url = 'https://example.com/api/v1/bundles?limit=50';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://example.com/api/v1/bundles?limit=50'Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters”Responses
Section titled “ Responses ”One page of bundles.
object
A folder that holds one or more spec docs and their assets.
object
The bundle folder relative to the served folder or the repo root.
The folder name.
The worst state of the bundle’s spec docs, for a list row: not_build_ready when one spec doc is Not Build Ready, then not_reviewed when one has no verdict on its current version, and build_ready only when every spec doc is Build Ready.
The spec docs of the bundle, by path.
One spec doc of a bundle, with its own profile, versions, review runs and verdict.
object
The bundle that holds the spec doc.
The profile of the spec doc.
Where a GitHub bundle comes from, and its draft (REQ-123).
object
The current version has changes that are not on GitHub.
GitHub changed after the draft started.
The path of the spec doc in its bundle.
object
The verdict of the bundle’s latest completed run. It is stale when that run is not on the current version.
object
Lint means only the lint stage ran.
object
Checks in adoption mode (REQ-133).
Open MUST findings.
Open blocking threads. Any makes the verdict Not Build Ready (§8.6 rule 2).
The full review whose AI findings this verdict counts. For a full run, the run itself.
The version the AI review read, when it is older than this verdict’s version.
How many sections changed since the AI review read the doc.
Set when the verdict is stale because a linked bundle has a newer version than the run read (REQ-056).
With stale_reason upstream_changed, the linked spec docs that have a newer version than the run read.
object
The bundle that holds the spec doc.
Why the latest run on the current version failed, when it failed.
The frontmatter keys the main doc does not name, and the values a review used for them (REQ-135). Absent when the doc names both.
object
The one thing the caller must do next on this bundle. Absent when nothing is open. The list carries the kind and the sentence; one bundle also carries the target.
object
What to do, in words, for a button label or a status line.
The key of the tour point to open.
Folders that are not valid bundles, for example with two main docs (REQ-001).
object
Example
{ "items": [ { "source_kind": "local", "visibility": "private", "state": "not_build_ready", "docs": [ { "source_kind": "local", "verdict": { "kind": "lint", "result": "build_ready", "stale_reason": "upstream_changed" }, "status": "draft", "next_action": { "kind": "waiver" } } ] } ]}default
Section titled “default”An error.
RFC 9457 problem details with a stable code.
object
A stable machine-readable error code.
Examplegenerated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example", "code": "example"}