GitLab API

Use these operations to interact with the GitLab integration in Cortex.

Required permissions

Your API key must have the Configure integrations permission.

Operations

Retrieve configurations

get
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Responses
get
/api/v1/gitlab/configurations

Retrieve default configuration

get
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Responses
get
/api/v1/gitlab/default-configuration

Retrieve a configuration

get
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Path parameters
aliasstringRequired
Responses
get
/api/v1/gitlab/configuration/{alias}

Add a single configuration

post
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Body
aliasstringRequired
groupNamesstring[]Required
hidePersonalProjectsbooleanRequired
hoststringOptional
isDefaultbooleanRequired
personalAccessTokenstringRequired
Responses
post
/api/v1/gitlab/configuration

Validate all configurations

post
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Responses
post
/api/v1/gitlab/configuration/validate

Validate a configuration

post
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Path parameters
aliasstringRequired
Responses
post
/api/v1/gitlab/configuration/validate/{alias}

Update a configuration

put

WARNING: Updating aliases for configurations or changing the default configuration could cause entity YAMLs that use this integration to break.

Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Path parameters
aliasstringRequired
Body
aliasstringRequired
groupNamesstring[]Required
hidePersonalProjectsbooleanRequired
hoststringOptional
isDefaultbooleanRequired
Responses
put
/api/v1/gitlab/configuration/{alias}

Add multiple configurations

post
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Body
Responses
post
/api/v1/gitlab/configurations

Delete all configurations

delete
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Responses
delete
/api/v1/gitlab/configurations

No content

Delete a configuration

delete
Authorizations
AuthorizationstringRequired

All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.

Path parameters
aliasstringRequired
Responses
delete
/api/v1/gitlab/configuration/{alias}

Last updated

Was this helpful?