List Review Playbooks

GET /review-playbooks

Every playbook the caller can reach, including the wider ones it resolves through.

A workspace caller sees its organization’s and the platform’s, because that is what most-specific-wins means (§10) — a listing that hid them would make “why did the review use those instructions” unanswerable from the API.

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
q	query	string | null	optional	substring of slug or name
scope	query	workspace | organization | platform | null	optional	the playbook’s own level
is_default	query	boolean | null	optional	—
is_active	query	boolean | null	optional	—
limit	query	integer	optional	Default 50. min 1 max 200
cursor	query	string | null	optional	—
offset	query	integer | null	optional	min 0

Responses

Status	Description	Body
200	Successful Response	Page_ReviewPlaybookView_
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X GET https://your-deployment.example.com/review-playbooks \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — Page_ReviewPlaybookView_

Field	Type		Notes
items	ReviewPlaybookView[]	required	—
next_cursor	string | null	optional	—
total	integer | null	optional	—