Reject an unsupported token-based integration provider
Authenticated JSON fallback for provider identifiers other than the dedicated GitLab and Bitbucket connect routes. Always returns 400 after scope and admin checks.
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
Provider identifier. GitLab and Bitbucket use their dedicated routes, every other value is rejected.
Response
Bad request.
Human-readable explanation of the error.
Stable machine-readable error code. insufficient_scope means the token does not hold the scope that this endpoint requires.
Scope that the caller must add to the token. Returned with the insufficient_scope code.
scans:read, scans:write, vulnerabilities:read, vulnerabilities:write, dependencies:read, schedules:read, schedules:write, assets:read, assets:write, organizations:read, organizations:write, members:read, members:write, invitations:read, invitations:write, webhooks:read, webhooks:write, tokens:write, audit:read, pr_reviews:read, pr_reviews:write, connectors:read, connectors:write, knowledge:read, knowledge:write, uploads:write, integrations:read, integrations:write, chat:read, chat:write, scans:message, analytics:read, llm:read, llm:write, test_users:read, test_users:write, license:read, supply_chain:read, supply_chain:write, billing:read, billing:write Documentation page that explains how to resolve the error.
One instruction that resolves the error. For insufficient_scope, a CLI session gets the strix cloud session scopes set full or strix cloud login --scope-profile full command, and an API token gets the settings page where the user creates a token with the scope. When the owner's role cannot hold the scope, the hint asks for a role change instead.