GitLab | Operate As Docs

Connect your client's GitLab with a sign-in, and call its API through Operate As.

Website: about.gitlab.com
Connects by: Signing in with GitLab
Category: Developer tools
Services: 1
Tools: 1,145

Service	Key	Base URL
GitLab	`gitlab`	`https://gitlab.com/api/v4`

Connecting

Your client presses Connect on their link and approves on GitLab's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "gitlab"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "gitlab"    ]  }]

Permissions

What the client reads	Permission it asks for
See and change your projects, issues and merge requests	`api`

Tools

Install GitLab's typed package for your language:

pip install operate-as-gitlab

pip install operate-as-gitlab

Run gitlab.delete_api_v4_admin_ci_variables_key

curl -X POST https://api.operate.as/v1/actions/gitlab.delete_api_v4_admin_ci_variables_key \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "key": "<key>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/gitlab.delete_api_v4_admin_ci_variables_key \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "key": "<key>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/gitlab.delete_api_v4_admin_ci_variables_key

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://gitlab.com/api/v4. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../gitlab/..." \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../gitlab/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If GitLab refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's GitLab access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's GitLab access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "gitlab",
    "services": [
      "gitlab"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "gitlab",    "services": [      "gitlab"    ],    "reconnectUrl": "https://…"  }}