Find API Clients for GitLab [on our website](https://about.gitlab.com/applications/#api-clients).
You can use [GitLab as an OAuth2 client](oauth2.md) to make API calls.
## Introduction
## Authentication
All API requests require authentication. You need to pass a `private_token` parameter by URL or header. If passed as header, the header name must be "PRIVATE-TOKEN" (capital and with dash instead of underscore). You can find or reset your private token in your profile.
All API requests require authentication. You need to pass a `private_token`
parameter by URL or header. If passed as a header, the header name must be
**PRIVATE-TOKEN** (capital and with dash instead of underscore). You can find
or reset your private token in your account page (`/profile/account`).
If no, or an invalid, `private_token` is provided then an error message will be returned with status code 401:
If `private_token` is invalid or omitted, then an error message will be
returned with status code `401`:
```json
{
...
...
@@ -44,71 +43,82 @@ If no, or an invalid, `private_token` is provided then an error message will be
}
```
API requests should be prefixed with `api` and the API version. The API version is defined in `lib/api.rb`.
API requests should be prefixed with `api` and the API version. The API version
is defined in `lib/api.rb`.
Example of a valid API request:
```
GET http://example.com/api/v3/projects?private_token=QVy1PB7sTxfy4pqfZM1U
```shell
GET https://gitlab.example.com/api/v3/projects?private_token=9koXpg98eAheJpvBs5tK
```
Example for a valid API request using curl and authentication via header:
Example of a valid API request using curl and authentication via header:
Read more about [GitLab as an OAuth2 client](oauth2.md).
## Status codes
The API is designed to return different status codes according to context and action. In this way if a request results in an error the caller is able to get insight into what went wrong, e.g. status code `400 Bad Request` is returned if a required attribute is missing from the request. The following list gives an overview of how the API functions generally behave.
API request types:
-`GET` requests access one or more resources and return the result as JSON
-`POST` requests return `201 Created` if the resource is successfully created and return the newly created resource as JSON
-`GET`, `PUT` and `DELETE` return `200 OK` if the resource is accessed, modified or deleted successfully, the (modified) result is returned as JSON
-`DELETE` requests are designed to be idempotent, meaning a request a resource still returns `200 OK` even it was deleted before or is not available. The reasoning behind it is the user is not really interested if the resource existed before or not.
The following list shows the possible return codes for API requests.
Return values:
-`200 OK` - The `GET`, `PUT` or `DELETE` request was successful, the resource(s) itself is returned as JSON
-`201 Created` - The `POST` request was successful and the resource is returned as JSON
-`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 is necessary, see above
-`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
-`422 Unprocessable` - The entity could not be processed
-`500 Server Error` - While handling the request something went wrong on the server side
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 | Explanation |
| ------------ | ----------- |
| `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. |
| `GET` / `PUT` / `DELETE` | Return `200 OK` if the resource is accessed, modified or deleted successfully. The (modified) result is returned as JSON. |
| `DELETE` | Designed to be idempotent, meaning a request to a resource still returns `200 OK` even it was deleted before or is not available. The reasoning behind it is the user is not really interested if the resource existed before or not. |
The following table shows the possible return codes for API requests.
| Return values | Explanation |
| ------------- | ----------- |
| `200 OK` | The `GET`, `PUT` or `DELETE` request was successful, the resource(s) itself is returned as JSON. |
| `201 Created` | The `POST` request was successful and the resource is returned as JSON. |
| `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. |
| `422 Unprocessable` | The entity could not be processed. |
| `500 Server Error` | While handling the request something went wrong on the server side. |
## Sudo
All API requests support performing an api call as if you were another user, if your private token is for an administration account. You need to pass `sudo` parameter by URL or header with an id or username of the user you want to perform the operation as. If passed as header, the header name must be "SUDO" (capitals).
All API requests support performing an API call as if you were another user,
provided your private token is from an administration account. You need to pass
the `sudo` parameter by URL or header with an ID or username of the user you
want to perform the operation as. If passed as a header, the header name must
be **SUDO** (capitals).
If a non administrative `private_token` is provided then an error message will be returned with status code 403:
If a non administrative `private_token` is provided, then an error message will
be returned with status code `403`:
```json
{
...
...
@@ -116,7 +126,8 @@ If a non administrative `private_token` is provided then an error message will b
}
```
If the sudo user id or username cannot be found then an error message will be returned with status code 404:
If the sudo user id or username cannot be found, an error message will be
returned with status code `404`:
```json
{
...
...
@@ -124,82 +135,113 @@ If the sudo user id or username cannot be found then an error message will be re
}
```
Example of a valid API with sudo request:
Example of a valid API call with sudo request providing a username and an ID
respectively:
```
GET http://example.com/api/v3/projects?private_token=QVy1PB7sTxfy4pqfZM1U&sudo=username
```shell
GET /projects?private_token=9koXpg98eAheJpvBs5tK&sudo=username
```
```
GET http://example.com/api/v3/projects?private_token=QVy1PB7sTxfy4pqfZM1U&sudo=23
```shell
GET /projects?private_token=9koXpg98eAheJpvBs5tK&sudo=23
```
Example for a valid API request with sudo using curl and authentication via header:
Example of a valid API request with sudo using curl and authentication via
When listing resources you can pass the following parameters:
Sometimes the returned result will span across many lines. When listing
resources you can pass the following parameters.
| Parameter | Description |
| --------- | ----------- |
| `page` | Page number (default: `1`). |
| `per_page`| Number of items to list per page (default: `20`, max: `100`). |
-`page` (default: `1`) - page number
-`per_page` (default: `20`, max: `100`) - number of items to list per page
In the example below, we list 50 [namespaces](namespaces.md) per page.
[Link headers](http://www.w3.org/wiki/LinkHeader) are send back with each response. These have `rel` prev/next/first/last and contain the relevant URL. Please use these instead of generating your own URLs.
```bash
curl -X PUT -H"PRIVATE-TOKEN: 9koXpg98eAheJpvBs5tK""https://gitlab.example.com/api/v3/namespaces?per_page=50
```
[Link headers](http://www.w3.org/wiki/LinkHeader) are sent back with each
response. These have `rel` prev/next/first/last and contain the relevant URL.
Please use these instead of generating your own URLs.
## id vs iid
When you work with API you may notice two similar fields in api entities: id and iid. The main difference between them is scope. Example:
When you work with the API, you may notice two similar fields in API entities:
`id` and `iid`. The main difference between them is scope.
For example, an issue might have `id: 46` and `iid: 5`.
Issue:
| Parameter | Description |
| --------- | ----------- |
| id | is unique across all issues and is used for any API call. |
| iid | is unique only in scope of a single project. When you browse issues or merge requests with Web UI, you see the `iid`. |
id: 46
iid: 5
That means that if you want to get an issue via the API you should use:
- id - is unique across all issues. It's used for any api call.
- iid - is unique only in scope of a single project. When you browse issues or merge requests with Web UI, you see iid.
So if you want to get issue with api you use `http://host/api/v3/.../issues/:id.json`. But when you want to create a link to web page - use `http:://host/project/issues/:iid.json`
On the other hand, if you want to create a link to a web page you should use:
