README.md 21 KB
Newer Older
1
# GitLab API
2

3
Automate GitLab via a simple and powerful API. All definitions can be found
4
under [`/lib/api`](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/lib/api).
5

6 7
The main GitLab API is a [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) API. Therefore, documentation in this section assumes knowledge of REST concepts.

8
## API Resources
9

10
The following API resources are available:
11

12 13 14
- [Applications](applications.md)
- [Avatar](avatar.md)
- [Award emoji](award_emoji.md)
15
- [Branches](branches.md)
16 17
- [Broadcast messages](broadcast_messages.md)
- [Code snippets](snippets.md)
18
- [Commits](commits.md)
19 20
- [Custom attributes](custom_attributes.md)
- [Deploy keys](deploy_keys.md), and [deploy keys for multiple projects](deploy_key_multiple_projects.md)
21
- [Deployments](deployments.md)
22
- [Discussions](discussions.md) (threaded comments)
23
- [Environments](environments.md)
Mark Fletcher's avatar
Mark Fletcher committed
24
- [Events](events.md)
25
- [Feature flags](features.md)
26 27 28 29 30 31 32 33
- Group-related resources, including:
  - [Groups](groups.md)
  - [Group access requests](access_requests.md)
  - [Group badges](group_badges.md)
  - [Group issue boards](group_boards.md)
  - [Group-level variables](group_level_variables.md)
  - [Group members](members.md)
  - [Group milestones](group_milestones.md)
34
- [Issues](issues.md)
35
- [Issue boards](boards.md)
36
- [Jobs](jobs.md)
37
- [Keys](keys.md)
38
- [Labels](labels.md)
39
- [Markdown](markdown.md)
40
- [Merge requests](merge_requests.md)
41
- [Namespaces](namespaces.md)
42
- [Notes](notes.md) (comments)
43
- [Notification settings](notification_settings.md)
44
- [Pages domains](pages_domains.md)
45
- [Pipelines](pipelines.md)
46 47 48 49 50 51
- [Pipeline schedules](pipeline_schedules.md)
- [Pipeline triggers](pipeline_triggers.md) and [triggering pipelines](../ci/triggers/README.md)
- Project-related resources, including:
  - [Projects](projects.md) including setting Webhooks
  - [Project access requests](access_requests.md)
  - [Project badges](project_badges.md)
52
  - [Project clusters](project_clusters.md)
53 54 55 56 57 58 59 60
  - [Project-level variables](project_level_variables.md)
  - [Project import/export](project_import_export.md)
  - [Project members](members.md)
  - [Project milestones](milestones.md)
  - [Project snippets](project_snippets.md)
  - [Project templates](project_templates.md) (see also [Templates API Resources](#templates-api-resources))
- [Protected branches](protected_branches.md)
- [Protected tags](protected_tags.md)
61
- [Repositories](repositories.md)
62 63 64
- [Repository files](repository_files.md)
- [Repository submodules](repository_submodules.md)
- [Resource label events](resource_label_events.md)
65
- [Runners](runners.md)
66
- [Search](search.md)
67 68
- [Services](services.md)
- [Settings](settings.md)
69
- [Sidekiq metrics](sidekiq_metrics.md)
70
- [System hooks](system_hooks.md)
71
- [Tags](tags.md)
72 73 74
- [Releases](releases/index.md)
- Release Assets
  - [Links](releases/links.md)
75
- [Todos](todos.md)
76
- [Users](users.md)
77
- [Validate CI configuration](lint.md) (linting)
78
- [Version](version.md)
79
- [Wikis](wikis.md)
80

81 82 83 84 85 86 87 88 89 90 91
See also [V3 to V4](v3_to_v4.md).

### Templates API Resources

Endpoints are available for:

- [Dockerfile templates](templates/dockerfiles.md).
- [gitignore templates](templates/gitignores.md).
- [GitLab CI YAML templates](templates/gitlab_ci_ymls.md).
- [Open source license templates](templates/licenses.md).

92 93
## Road to GraphQL

94 95 96 97 98
Going forward, we will start on moving to
[GraphQL](http://graphql.org/learn/best-practices/) and deprecate the use of
controller-specific endpoints. GraphQL has a number of benefits:

1. We avoid having to maintain two different APIs.
99 100
1. Callers of the API can request only what they need.
1. It is versioned by default.
101 102 103 104 105 106 107 108

It will co-exist with the current v4 REST API. If we have a v5 API, this should
be a compatibility layer on top of GraphQL.

Although there were some patenting and licensing concerns with GraphQL, these
have been resolved to our satisfaction by the relicensing of the reference
implementations under MIT, and the use of the OWF license for the GraphQL
specification.
109

110 111 112
## Compatibility Guidelines

The HTTP API is versioned using a single number, the current one being 4. This
113
number symbolizes the same as the major version number as described by
114 115
[SemVer](https://semver.org/). This mean that backward incompatible changes
will require this version number to change. However, the minor version is
116
not explicit. This allows for a stable API endpoint, but also means new
117 118 119
features can be added to the API in the same version number.

New features and bug fixes are released in tandem with a new GitLab, and apart
Bruce Szalwinski's avatar
Bruce Szalwinski committed
120
from incidental patch and security releases, are released on the 22nd of each
121 122 123 124
month. Backward incompatible changes (e.g. endpoints removal, parameters
removal etc.), as well as removal of entire API versions are done in tandem
with a major point release of GitLab itself. All deprecations and changes
between two versions should be listed in the documentation. For the changes
125 126
between v3 and v4; please read the [v3 to v4 documentation](v3_to_v4.md)

127
### Current status
128

129
Currently only API version v4 is available. Version v3 was removed in
130 131
[GitLab 11.0](https://gitlab.com/gitlab-org/gitlab-ce/issues/36819).

132 133 134
## Basic usage

API requests should be prefixed with `api` and the API version. The API version
135 136
is defined in [`lib/api.rb`][lib-api-url]. For example, the root of the v4 API
is at `/api/v4`.
137

Douwe Maan's avatar
Douwe Maan committed
138
Example of a valid API request using cURL:
139 140

```shell
Douwe Maan's avatar
Douwe Maan committed
141
curl "https://gitlab.example.com/api/v4/projects"
142 143 144 145 146
```

The API uses JSON to serialize data. You don't need to specify `.json` at the
end of an API URL.

147
## Authentication
148

Douwe Maan's avatar
Douwe Maan committed
149 150
Most API requests require authentication, or will only return public data when
authentication is not provided. For
151 152
those cases where it is not required, this will be mentioned in the documentation
for each individual endpoint. For example, the [`/projects/:id` endpoint](projects.md).
153

Douwe Maan's avatar
Douwe Maan committed
154
There are three ways to authenticate with the GitLab API:
155

156 157
1. [OAuth2 tokens](#oauth2-tokens)
1. [Personal access tokens](#personal-access-tokens)
Douwe Maan's avatar
Douwe Maan committed
158 159 160
1. [Session cookie](#session-cookie)

For admins who want to authenticate with the API as a specific user, or who want to build applications or scripts that do so, two options are available:
161

Douwe Maan's avatar
Douwe Maan committed
162
1. [Impersonation tokens](#impersonation-tokens)
163
1. [Sudo](#sudo)
164

165 166
If authentication information is invalid or omitted, an error message will be
returned with status code `401`:
167 168 169 170 171 172 173

```json
{
  "message": "401 Unauthorized"
}
```

Douwe Maan's avatar
Douwe Maan committed
174
### OAuth2 tokens
175

Douwe Maan's avatar
Douwe Maan committed
176 177
You can use an [OAuth2 token](oauth2.md) to authenticate with the API by passing it in either the
`access_token` parameter or the `Authorization` header.
178

Douwe Maan's avatar
Douwe Maan committed
179
Example of using the OAuth2 token in a parameter:
180

Douwe Maan's avatar
Douwe Maan committed
181 182 183
```shell
curl https://gitlab.example.com/api/v4/projects?access_token=OAUTH-TOKEN
```
184

Douwe Maan's avatar
Douwe Maan committed
185
Example of using the OAuth2 token in a header:
186

187
```shell
188
curl --header "Authorization: Bearer OAUTH-TOKEN" https://gitlab.example.com/api/v4/projects
189 190
```

Douwe Maan's avatar
Douwe Maan committed
191
Read more about [GitLab as an OAuth2 provider](oauth2.md).
192

Douwe Maan's avatar
Douwe Maan committed
193
### Personal access tokens
194

Douwe Maan's avatar
Douwe Maan committed
195 196
You can use a [personal access token][pat] to authenticate with the API by passing it in either the
`private_token` parameter or the `Private-Token` header.
197

Douwe Maan's avatar
Douwe Maan committed
198
Example of using the personal access token in a parameter:
199

Douwe Maan's avatar
Douwe Maan committed
200
```shell
201
curl https://gitlab.example.com/api/v4/projects?private_token=<your_access_token>
Douwe Maan's avatar
Douwe Maan committed
202 203 204
```

Example of using the personal access token in a header:
205

Douwe Maan's avatar
Douwe Maan committed
206
```shell
207
curl --header "Private-Token: <your_access_token>" https://gitlab.example.com/api/v4/projects
Douwe Maan's avatar
Douwe Maan committed
208
```
209

Douwe Maan's avatar
Douwe Maan committed
210 211 212 213 214 215 216
Read more about [personal access tokens][pat].

### Session cookie

When signing in to the main GitLab application, a `_gitlab_session` cookie is
set. The API will use this cookie for authentication if it is present, but using
the API to generate a new session cookie is currently not supported.
217

Douwe Maan's avatar
Douwe Maan committed
218 219 220
The primary user of this authentication method is the web frontend of GitLab itself,
which can use the API as the authenticated user to get a list of their projects,
for example, without needing to explicitly pass an access token.
221

222
### Impersonation tokens
223

224
> [Introduced][ce-9099] in GitLab 9.0. Needs admin permissions.
225

226
Impersonation tokens are a type of [personal access token][pat]
Douwe Maan's avatar
Douwe Maan committed
227 228
that can only be created by an admin for a specific user. They are a great fit
if you want to build applications or scripts that authenticate with the API as a specific user.
229

Douwe Maan's avatar
Douwe Maan committed
230 231 232
They are an alternative to directly using the user's password or one of their
personal access tokens, and to using the [Sudo](#sudo) feature, since the user's (or admin's, in the case of Sudo)
password/token may not be known or may change over time.
233

234
For more information, refer to the
235
[users API](users.md#retrieve-user-impersonation-tokens) docs.
236

Douwe Maan's avatar
Douwe Maan committed
237 238
Impersonation tokens are used exactly like regular personal access tokens, and can be passed in either the
`private_token` parameter or the `Private-Token` header.
239

240 241 242 243 244
#### Disable impersonation

> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/40385) in GitLab
11.6.

245
By default, impersonation is enabled. To disable impersonation:
246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275

**For Omnibus installations**

1. Edit `/etc/gitlab/gitlab.rb`:

    ```ruby
    gitlab_rails['impersonation_enabled'] = false
    ```

1. Save the file and [reconfigure](../administration/restart_gitlab.md#omnibus-gitlab-reconfigure)
   GitLab for the changes to take effect.

To re-enable impersonation, remove this configuration and reconfigure GitLab.

---

**For installations from source**

1. Edit `config/gitlab.yml`:

    ```yaml
    gitlab:
      impersonation_enabled: false
    ```

1. Save the file and [restart](../administration/restart_gitlab.md#installations-from-source)
   GitLab for the changes to take effect.

To re-enable impersonation, remove this configuration and restart GitLab.

276
### Sudo
277

278
NOTE: **Note:**
279
Only available to [administrators](../user/permissions.md).
280

281
All API requests support performing an API call as if you were another user,
Douwe Maan's avatar
Douwe Maan committed
282 283 284
provided you are authenticated as an administrator with an OAuth or Personal Access Token that has the `sudo` scope.

You need to pass the `sudo` parameter either via query string or a header with an ID/username of
285
the user you want to perform the operation as. If passed as a header, the
286
header name must be `Sudo`.
287 288 289

NOTE: **Note:**
Usernames are case insensitive.
290

Douwe Maan's avatar
Douwe Maan committed
291
If a non administrative access token is provided, an error message will
292
be returned with status code `403`:
293 294 295

```json
{
296
  "message": "403 Forbidden - Must be admin to use sudo"
297 298 299
}
```

Douwe Maan's avatar
Douwe Maan committed
300 301 302 303 304 305 306 307 308 309 310
If an access token without the `sudo` scope is provided, an error message will
be returned with status code `403`:

```json
{
  "error": "insufficient_scope",
  "error_description": "The request requires higher privileges than provided by the access token.",
  "scope": "sudo"
}
```

311
If the sudo user ID or username cannot be found, an error message will be
312
returned with status code `404`:
313 314 315

```json
{
Douwe Maan's avatar
Douwe Maan committed
316
  "message": "404 User with ID or username '123' Not Found"
317 318 319
}
```

320 321 322 323
---

Example of a valid API call and a request using cURL with sudo request,
providing a username:
324

325
```
326
GET /projects?private_token=<your_access_token>&sudo=username
327
```
328

329
```shell
330
curl --header "Private-Token: <your_access_token>" --header "Sudo: username" "https://gitlab.example.com/api/v4/projects"
331 332
```

333 334
Example of a valid API call and a request using cURL with sudo request,
providing an ID:
335

336
```
337
GET /projects?private_token=<your_access_token>&sudo=23
338
```
339

340
```shell
341
curl --header "Private-Token: <your_access_token>" --header "Sudo: 23" "https://gitlab.example.com/api/v4/projects"
342
```
343

344 345 346 347 348 349 350 351 352 353 354 355
## Status codes

The API is designed to return different status codes according to context and
action. This way, if a request results in an error, the caller is able to get
insight into what went wrong.

The following table gives an overview of how the API functions generally behave.

| Request type | Description |
| ------------ | ----------- |
| `GET`   | Access one or more resources and return the result as JSON. |
| `POST`  | Return `201 Created` if the resource is successfully created and return the newly created resource as JSON. |
356
| `GET` / `PUT` | Return `200 OK` if the resource is accessed or modified successfully. The (modified) result is returned as JSON. |
Pascal Borreli's avatar
Pascal Borreli committed
357
| `DELETE` | Returns `204 No Content` if the resource was deleted successfully. |
358 359 360 361 362 363 364 365 366 367 368 369 370 371 372

The following table shows the possible return codes for API requests.

| Return values | Description |
| ------------- | ----------- |
| `200 OK` | The `GET`, `PUT` or `DELETE` request was successful, the resource(s) itself is returned as JSON. |
| `204 No Content` | The server has successfully fulfilled the request and that there is no additional content to send in the response payload body. |
| `201 Created` | The `POST` request was successful and the resource is returned as JSON. |
| `304 Not Modified` | Indicates that the resource has not been modified since the last request. |
| `400 Bad Request` | A required attribute of the API request is missing, e.g., the title of an issue is not given. |
| `401 Unauthorized` | The user is not authenticated, a valid [user token](#authentication) is necessary. |
| `403 Forbidden` | The request is not allowed, e.g., the user is not allowed to delete a project. |
| `404 Not Found` | A resource could not be accessed, e.g., an ID for a resource could not be found. |
| `405 Method Not Allowed` | The request is not supported. |
| `409 Conflict` | A conflicting resource already exists, e.g., creating a project with a name that already exists. |
Robert Schilling's avatar
Robert Schilling committed
373
| `412` | Indicates the request was denied. May happen if the `If-Unmodified-Since` header is provided when trying to delete a resource, which was modified in between. |
374 375
| `422 Unprocessable` | The entity could not be processed. |
| `500 Server Error` | While handling the request something went wrong server-side. |
376

Dmitriy Zaporozhets's avatar
Dmitriy Zaporozhets committed
377
## Pagination
Nihad Abbasov's avatar
Nihad Abbasov committed
378

379 380
Sometimes the returned result will span across many pages. When listing
resources you can pass the following parameters:
Nihad Abbasov's avatar
Nihad Abbasov committed
381

382 383
| Parameter | Description |
| --------- | ----------- |
384 385
| `page`    | Page number (default: `1`) |
| `per_page`| Number of items to list per page (default: `20`, max: `100`) |
Nihad Abbasov's avatar
Nihad Abbasov committed
386

387 388 389
In the example below, we list 50 [namespaces](namespaces.md) per page.

```bash
390
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/namespaces?per_page=50
391 392
```

393
### Pagination Link header
394

395
[Link headers](http://www.w3.org/wiki/LinkHeader) are sent back with each
396 397
response. They have `rel` set to prev/next/first/last and contain the relevant
URL. Please use these links instead of generating your own URLs.
398

399 400 401 402 403
In the cURL example below, we limit the output to 3 items per page (`per_page=3`)
and we request the second page (`page=2`) of [comments](notes.md) of the issue
with ID `8` which belongs to the project with ID `8`:

```bash
404
curl --head --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/8/issues/8/notes?per_page=3&page=2
405 406
```

407 408 409 410 411 412 413 414
The response will then be:

```
HTTP/1.1 200 OK
Cache-Control: no-cache
Content-Length: 1103
Content-Type: application/json
Date: Mon, 18 Jan 2016 09:43:18 GMT
415
Link: <https://gitlab.example.com/api/v4/projects/8/issues/8/notes?page=1&per_page=3>; rel="prev", <https://gitlab.example.com/api/v4/projects/8/issues/8/notes?page=3&per_page=3>; rel="next", <https://gitlab.example.com/api/v4/projects/8/issues/8/notes?page=1&per_page=3>; rel="first", <https://gitlab.example.com/api/v4/projects/8/issues/8/notes?page=3&per_page=3>; rel="last"
416 417 418 419 420 421 422 423 424 425
Status: 200 OK
Vary: Origin
X-Next-Page: 3
X-Page: 2
X-Per-Page: 3
X-Prev-Page: 1
X-Request-Id: 732ad4ee-9870-4866-a199-a9db0cde3c86
X-Runtime: 0.108688
X-Total: 8
X-Total-Pages: 3
426 427 428 429
```

### Other pagination headers

430 431 432 433 434 435 436 437 438 439
Additional pagination headers are also sent back.

| Header | Description |
| ------ | ----------- |
| `X-Total`       | The total number of items |
| `X-Total-Pages` | The total number of pages |
| `X-Per-Page`    | The number of items per page |
| `X-Page`        | The index of the current page (starting at 1) |
| `X-Next-Page`   | The index of the next page |
| `X-Prev-Page`   | The index of the previous page |
440

441 442
## Namespaced path encoding

443
If using namespaced API calls, make sure that the `NAMESPACE/PROJECT_NAME` is
444 445
URL-encoded.

446
For example, `/` is represented by `%2F`:
447 448

```
449 450 451
GET /api/v4/projects/diaspora%2Fdiaspora
```

452
## Branches and tags name encoding
453 454 455 456 457 458 459 460

If your branch or tag contains a `/`, make sure the branch/tag name is
URL-encoded.

For example, `/` is represented by `%2F`:

```
GET /api/v4/projects/1/branches/my%2Fbranch/commits
461 462
```

463 464
## Encoding API parameters of `array` and `hash` types

465
We can call the API with `array` and `hash` types parameters as shown below:
466 467 468 469 470

### `array`

`import_sources` is a parameter of type `array`:

471
```bash
472
curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \
473 474 475 476 477 478 479 480 481
-d "import_sources[]=github" \
-d "import_sources[]=bitbucket" \
"https://gitlab.example.com/api/v4/some_endpoint
```

### `hash`

`override_params` is a parameter of type `hash`:

482
```bash
483
curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \
484 485 486 487 488 489 490 491
--form "namespace=email" \
--form "path=impapi" \
--form "file=@/path/to/somefile.txt"
--form "override_params[visibility]=private" \
--form "override_params[some_other_param]=some_value" \
https://gitlab.example.com/api/v4/projects/import
```

492 493 494 495 496 497 498 499 500 501 502 503 504 505
### Array of hashes

`variables` is a parameter of type `array` containing hash key/value pairs `[{ 'key' => 'UPLOAD_TO_S3', 'value' => 'true' }]`:

```bash
curl --globoff --request POST --header "PRIVATE-TOKEN: ********************" \
"https://gitlab.example.com/api/v4/projects/169/pipeline?ref=master&variables[][key]=VAR1&variables[][value]=hello&variables[][key]=VAR2&variables[][value]=world"

curl --request POST --header "PRIVATE-TOKEN: ********************" \
--header "Content-Type: application/json" \
--data '{ "ref": "master", "variables": [ {"key": "VAR1", "value": "hello"}, {"key": "VAR2", "value": "world"} ] }' \
"https://gitlab.example.com/api/v4/projects/169/pipeline"
```

506
## `id` vs `iid`
Dmitriy Zaporozhets's avatar
Dmitriy Zaporozhets committed
507

508
 Some resources have two similarly-named fields. For example, [issues](issues.md), [merge requests](merge_requests.md), and [project milestones](merge_requests.md). The fields are:
509

510 511
- `id`: ID that is unique across all projects.
- `iid`: additional, internal ID that is unique in the scope of a single project.
512

513 514
NOTE: **Note:**
The `iid` is displayed in the web UI.
Dmitriy Zaporozhets's avatar
Dmitriy Zaporozhets committed
515

516
If a resource has the `iid` field and the `id` field, the `iid` field is usually used instead of `id` to fetch the resource.
517

518
For example, suppose a project with `id: 42` has an issue with `id: 46` and `iid: 5`. In this case:
Dmitriy Zaporozhets's avatar
Dmitriy Zaporozhets committed
519

520 521
- A valid API call to retrieve the issue is  `GET /projects/42/issues/5`
- An invalid API call to retrieve the issue is `GET /projects/42/issues/46`.
Dmitriy Zaporozhets's avatar
Dmitriy Zaporozhets committed
522

523
NOTE: **Note:**
524
Not all resources with the `iid` field are fetched by `iid`. For guidance on which field to use, see the documentation for the specific resource.
525 526 527

## Data validation and error reporting

528
When working with the API you may encounter validation errors, in which case
529 530
the API will answer with an HTTP `400` status.

531 532
Such errors appear in two cases:

533
- A required attribute of the API request is missing, e.g., the title of an
534
  issue is not given
535
- An attribute did not pass the validation, e.g., user bio is too long
536 537 538

When an attribute is missing, you will get something like:

539
```
540 541 542 543 544 545
HTTP/1.1 400 Bad Request
Content-Type: application/json
{
    "message":"400 (Bad request) \"title\" not given"
}
```
546

547 548
When a validation error occurs, error messages will be different. They will
hold all details of validation errors:
549

550
```
551 552 553 554 555 556 557
HTTP/1.1 400 Bad Request
Content-Type: application/json
{
    "message": {
        "bio": [
            "is too long (maximum is 255 characters)"
        ]
558
    }
559 560
}
```
561

562 563
This makes error messages more machine-readable. The format can be described as
follows:
564

565 566 567 568 569 570 571 572 573
```json
{
    "message": {
        "<property-name>": [
            "<error-message>",
            "<error-message>",
            ...
        ],
        "<embed-entity>": {
574 575 576 577 578 579 580
            "<property-name>": [
                "<error-message>",
                "<error-message>",
                ...
            ],
        }
    }
581 582 583
}
```

584
## Unknown route
585

586
When you try to access an API URL that does not exist you will receive 404 Not Found.
587 588

```
589
HTTP/1.1 404 Not Found
590
Content-Type: application/json
591
{
592
    "error": "404 Not Found"
593 594 595
}
```

596 597 598
## Encoding `+` in ISO 8601 dates

If you need to include a `+` in a query parameter, you may need to use `%2B` instead due
Connor Shea's avatar
Connor Shea committed
599
a [W3 recommendation](http://www.w3.org/Addressing/URL/4_URI_Recommentations.html) that
600 601 602 603 604 605 606 607 608 609 610 611 612
causes a `+` to be interpreted as a space. For example, in an ISO 8601 date, you may want to pass
a time in Mountain Standard Time, such as:

```
2017-10-17T23:11:13.000+05:30
```

The correct encoding for the query parameter would be:

```
2017-10-17T23:11:13.000%2B05:30
```

613 614 615
## Clients

There are many unofficial GitLab API Clients for most of the popular
616
programming languages. Visit the [GitLab website] for a complete list.
617

618 619
[GitLab website]: https://about.gitlab.com/applications/#api-clients "Clients using the GitLab API"
[lib-api-url]: https://gitlab.com/gitlab-org/gitlab-ce/tree/master/lib/api/api.rb
620
[ce-3749]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3749
621
[ce-5951]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5951
622
[ce-9099]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9099
623
[pat]: ../user/profile/personal_access_tokens.md