Finishes connecting a GitLab account: GitLab sends the browser back with a code and the state you got from the overview.
HTTP
POST /integrations/gitlab/connectionsAccess: Session token only. API keys get 403 with insufficient_scope.
Role: Organisation owner or admin.
Request body #
JSON.
| Field | Type | Required | Description |
|---|---|---|---|
code | string | yes | The code GitLab sent back to the browser. |
state | string | yes | The state from connectUrl. |
JSON
{ "code": "...", "state": "..." }Response 200 #
The overview after connecting, as in GitLab overview.
Errors #
| Status | error | When |
|---|---|---|
| 401 | unauthenticated | The token is missing or not valid. |
| 403 | forbidden | You are not an owner or admin. |
| 503 | gitlab_not_configured | The GitLab integration is not set up on this server. |
| 400 | invalid_state | state is not the one the overview gave you, or was made by someone else. |
| 502 | gitlab_error | GitLab refused the request. message says why. |
| 429 | rate_limited | Too many requests, see Rate limiting. |
See Errors for the error format.