List approval gates (pending-approvals feed) for the authenticated org.
Returns approval gates scoped to the authenticated org, optionally filtered by issue or status. Gates that carry an MCP-tool project scope are additionally filtered to those the caller can access, so a project-scoped key or a non-member session never sees another project's gates. Ordered by createdAt ASC (pipeline stage order); the client groups by issue and sorts groups by urgency.
AuthorizationBearer <rsk_live_*>Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.
orgId?stringExplicit organization id; requires membership.
projectId?stringFilter to gates durably bound to this project.
issueId?stringFilter to a single issue id.
status?stringFilter by gate status.
"pending""in_review""approved""rejected""escalated""timed_out""superseded"Approval gates for the org.
application/json- response
gates*array<>curl -X GET 'https://app.rensei.ai/api/approval-gates'{ "gates": [ { "id": "string", "workspaceId": "string", "projectId": "string", "issueId": "string", "name": "string", "gateType": "string", "status": "pending", "requiredRoles": [ "string" ], "requiredCount": 0, "metadata": { "property1": null, "property2": null }, "createdAt": "string", "context": { "property1": null, "property2": null }, "property1": null, "property2": null } ]}Accept a current source version for an installed reference agent card.
Transactionally re-pins the install and re-materializes its projection. Every changed or removed upstream field with a local overlay requires an explicit keep-local or use-upstream decision.
Create an approval gate for the authenticated organization.
Create an approval gate for the authenticated organization. - Rensei REST API operation reference.