Create an external issue on a connected VCS repository

POST 
/api/v1/integrations/vcs/repositories/:repository_id/issues

Admin/API-key surface for batch flows. The user-facing path is POST /findings/{finding_id}/external-issues.

Issue creation is a write action against the upstream VCS, so JWT callers must additionally hold manager-or-above role (API-key callers are already gated by the integrations:manage scope). Visibility is enforced via repository access check; the provider's enforces the per-repo install safety contract.

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.