Skip to main content
List connected integrations, and connect GitLab or Bitbucket with a personal access token. GitHub App and Slack installations use interactive approval flows. The API and CLI return an installation link for a person to approve; neither completes that approval automatically. Validate, connect, install, and disconnect operations require an organization admin.

List integrations

Required scope: integrations:read

Validate a token

Validate a token before you connect (this operation does not store data):
Required scope: integrations:write Invalid or rejected provider credentials return HTTP 422 Unprocessable Entity. A provider outage or other upstream validation failure returns 502 Bad Gateway. HTTP 401 Unauthorized means the Strix API token used for this request is invalid; it is not how an invalid GitLab or Bitbucket credential is reported. GitHub and Slack require a person to approve an installation. Request the handoff URL like this:
Required scope: integrations:write The response contains url. Opening it is a separate human step; receiving the URL does not install or authorize the integration. The CLI equivalent is strix cloud integrations install github (or slack); add --no-browser to print the URL without opening it.

Connect with a token

For Bitbucket, use the bitbucket endpoints and pass the account email:
Required scope: integrations:write CLI equivalents keep the provider credential separate from the Strix API token used for authentication:

Disconnect an integration

<PROVIDER> is one of github, gitlab, bitbucket, or slack. GitHub, GitLab, and Bitbucket can have multiple installations, so pass the integer installation_id returned by the list endpoint:
Omit installation_id for organization-wide providers such as Slack. Passing it for Slack, or omitting it for GitHub, GitLab, or Bitbucket, returns 400 Bad Request. Required scope: integrations:write CLI equivalents: