GitLab CI/CD merge_request_approvals API
Operations about merge_request_approvals
GitLab CI/CD merge_request_approvals API is one of 98 APIs that GitLab CI/CD publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.
This API exposes 6 operations across 5 paths, and defines 15 schemas. It is described by OpenAPI 2.0, at version v4.
Requests are made against the base URL https://gitlab.com/api/v4.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
GitLab CI/CD merge_request_approvals API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as PRIVATE-TOKEN (access_token_header).
An API key is passed in the query as private_token (access_token_query).
Paths & Operations 6
Across 5 paths, the API surfaces 6 operations — 2 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Operations about mergerequestapprovals
Schemas 15
The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are API_Entities_Group (50 properties), API_Entities_ApprovalState (24 properties), API_Entities_MergeRequestApprovalStateRule (15 properties), API_Entities_Namespace_RootStorageStatistics (12 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from GitLab CI/CD 12
Other APIs GitLab CI/CD publishes across the network.
This is an independent, third-party profile of GitLab CI/CD merge_request_approvals API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.