Update integration settings
Updates settings for the Linear, Jira or Slack integration. For Linear and Jira, set issue_label_enabled and issue_label_name to add a label to each issue that Strix creates. For Slack, any channel id set on slack_default_channel_id or slack_channel_groups must be one Strix can post to: public channels are joined automatically, private channels need @Strix invited first. Personal tokens must belong to an organization administrator (parity with the dashboard).
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
Body
- Option 1
- Option 2
Updates for a Linear or Jira integration.
Finding sources that auto-sync creates tickets for (at least one): scan (pentest findings) and/or supply_chain (dependency CVEs). Set auto_sync_enabled to false to stop all auto-sync. Manual, bulk, and API pushes ignore this.
1scan, supply_chain Which dependency findings auto-create tickets. all (the default) tickets every dependency finding; reachable_only tickets only the findings whose reachability verdict is reachable; findings marked not_reachable or not_applicable, and findings still waiting for a verdict, get no ticket. Pentest findings ignore this. Manual, bulk, and API pushes ignore this.
all, reachable_only Destination for each routed repository. Applies to Linear and Jira. This array replaces the stored repository routes: a repository that is not in the array loses its route. Send collection_id (the older project_id name is still accepted). For Jira, ticket_type and jira_field_values are optional and Strix rejects a route that misses a required field. Administrators only.
- Option 1
- Option 2
The destination for each finding source, keyed by scan (pentests), pr_review, and supply_chain. Applies to Linear and Jira. This object replaces the stored routes. To use the default destination for a source, set the key to null or leave the key out. Resolution order on a push: explicit destination on the push request, then repository route, then source route, then the default destination.
Response
Updated integration settings (Linear, Jira) or {"success": true} (Slack).
- Option 1
- Option 2
Ticketing settings for a Linear or Jira integration.