Update Repo Binding

PATCH /repo-bindings/{binding_id}

404 on an unknown id. Never an upsert.

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
binding_id	path	string (uuid)	required	—

Request body — RepoBindingPatch

Field	Type		Notes
reviewer_agent_id	string (uuid) | null	optional	—
editor_agent_id	string (uuid) | null	optional	—
enabled_events	string[] | null	optional	—
review_config	object | null	optional	—
editor_config	object | null	optional	—
budget_config	object | null	optional	—
workspace_config	object | null	optional	—
is_active	boolean | null	optional	—

Responses

Status	Description	Body
200	Successful Response	RepoBindingView
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 PATCH https://your-deployment.example.com/repo-bindings/{binding_id} \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — RepoBindingView

Field	Type		Notes
id	string (uuid)	required	—
installation_id	integer	required	—
repo_full_name	string	required	—
reviewer_agent_id	string (uuid) | null	required, nullable	—
editor_agent_id	string (uuid) | null	required, nullable	—
enabled_events	object[]	required	—
review_config	object	required	—
editor_config	object	required	—
budget_config	object	required	—
workspace_config	object	required	—
is_active	boolean	required	—
organization_id	string (uuid)	required	—
workspace_id	string (uuid)	required	—
created_at	string (date-time)	required	—
updated_at	string (date-time)	required	—