ReviewIQ supports GitHub, GitLab, Bitbucket (Cloud and Data Center) and Azure DevOps. Credentials are encrypted at rest and validated with a live API call before the integration is saved.

GitHub

Token: a personal access token with the repo scope (plus webhook permission).
Account: your organization or user login, e.g. acme-inc.
Base URL: leave blank for github.com; set it for Enterprise Server.

GitLab

Token: a personal or project access token with the api scope.
Account: the group or namespace path, e.g. acme/platform.
Base URL: blank for gitlab.com; set it for self-managed.

Bitbucket Cloud

Email: the Atlassian account email the token belongs to — required. Bitbucket authenticates as email:token.
Token: an Atlassian API token (id.atlassian.com → Security → API tokens).
Account: the workspace ID, e.g. acme-workspace.

Bitbucket Data Center

Token: an HTTP access token used alone, or a password combined with a username.
Base URL: required, e.g. https://git.acme.com.

Azure DevOps

Token: a personal access token with Code (read) and Pull Request scopes.
Account: the organization, or organization/project.

If it fails

Errors are specific on purpose. A wrong token returns "rejected the credentials (401)", a workspace you can't see returns 404 with the workspace named, and an out-of-scope token returns 403 explaining which permission is missing.