Start the GitLab OAuth flow
POST/api/v1/integrations/gitlab/connect
Mint a signed state token and return the GitLab OAuth authorize URL.
Clients redirect the browser to the returned redirect_url. After the
user completes OAuth, GitLab redirects back to
/integrations/gitlab/callback with the authorization code.
- Scope required:
integrations:manage.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.