Export a vulnerability to a ticketing provider
Creates or syncs a Jira or Linear ticket for the vulnerability using the organization’s connected ticketing integration. If a ticket already exists for the vulnerability and provider, its status is synced instead of creating a duplicate.
Authorizations
API token obtained from the Tokens endpoint or CLI device login. Include as Authorization: Bearer <token>. Requests made with a managed CLI session also include X-Strix-Workspace: <organization_id> to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch.
Path Parameters
ID of the vulnerability. Use the id field of a finding from listVulnerabilities.
Body
Response
Ticket created or synced. fix_pr_link reports whether the finding's existing fix PR was attached to the ticket: attached, unsupported (connection cannot carry PR links), failed, or null when the finding has no fix PR. warning is present when the ticket was created without its pentest epic or project and explains why.
The response is of type object.