GitLab REST API
- REST API OpenAPI v3
Vendor coverage
GitLab API changes & breaking changes
GitLab announces deprecations continuously but concentrates breaking API changes into its annual major release each May. Detektu diffs the published REST API spec so the bundle of removals never lands unreviewed.
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How GitLab ships changes
The release patterns that shape your integration risk.
GitLab's REST API (v4) evolves additively during the year, with deprecations announced per milestone and removals reserved for major releases like 17.0 and 18.0. That model is friendly, provided you review the deprecation list. In practice, the list is long and mostly irrelevant to any one integration.
Detektu turns the spec diff into per-endpoint findings and matches them against your declared usage, so the yearly removal bundle becomes a short, reviewed list instead of a release-day scramble.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Endpoint parameter deprecated ahead of the next major
openapi:GET /api/v4/projects ::with_issues_enabledDeprecated attribute removed in the major release
openapi:GET /api/v4/users/{id} ::response.200.theme_idMonitored for you
Do GitLab's changes affect your integration?
Choose the operations and fields your services use. Detektu matches GitLab findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.