REST API Docs Internal Beta Launch
## DRI
@cfeick
## Participants
- @abignotti
- @vwolanyk
- @mwoolf
## Problem Statement
In https://gitlab.com/groups/gitlab-org/quality/-/work_items/261+, the API Platform team delivered an experimental deployment of GitLab's REST API documentation using OpenAPI 3.0 and Scalar. The outcome of that epic validated the problem solution and technical approach, however, it does not yet meet quality standards for production-readiness.
This epic tracks the work to deliver a beta-ready deployment to replace the legacy API documentation that is continuously deployed, secure, performant, and publicly available.
Note: API documentation rendered by Scalar is intentionally _not_ packaged for self-managed instances, so does not have to go through the PREP process.
## Exit Criteria
- [x] **Infrastructure**: production-ready continuous deployments, performance
- [x] **User experience**: branding parity, live API testing
- [x] **Stakeholders**: Beta launch communicated
- [x] **Migration**: api.gitlab.com/rest live
## Development Log
<!-- STATUS NOTE START -->
## Status 2026-05-07
:clock1: **total hours spent this week by all contributors**: 39
:tada: **achievements**:
- Project complete
**Closing Status**
**Original Problem**: GitLab's REST API documentation was served from manually maintained Markdown pages with no interactivity and no support for EE endpoints. The experimental deployment in [&261](https://gitlab.com/groups/gitlab-org/quality/-/work_items/261) validated the OpenAPI 3.0 + Scalar approach, but did not yet meet quality standards for a production-ready, publicly accessible deployment.
**Changes Made**: The team built a continuously deployed API documentation site on top of the foundation established in [&261](https://gitlab.com/groups/gitlab-org/quality/-/work_items/261). This included automating daily spec fetches from `gitlab-org/gitlab`, applying docs.gitlab.com branding with full theme and mobile parity, configuring the `api.gitlab.com/rest/` domain, enabling CORS for live API testing, adding a Beta status indicator with a link to the feedback issue, and establishing a testing strategy with unit and e2e coverage. The Internal Beta was announced to GitLab team members this week, and we are now actively collecting feedback.
**Impact**: Scalar is now live as GitLab's first continuously deployed, interactive REST API reference covering the full API surface area including EE endpoints. The deployment is secure, performant, and publicly accessible as an Internal Beta. Team members can explore the docs and share feedback in [api-docs#21](https://gitlab.com/gitlab-com/gl-infra/api-docs/-/work_items/21), while remaining work has been moved to [&402](https://gitlab.com/groups/gitlab-org/quality/-/work_items/402) for follow-up iterations.
**Demo**: https://api.gitlab.com/rest
Shout-out to `@mwoolf` `@abignotti` `@vwolanyk` for their contributions :rocket:
**Please close epic during grand review**
_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/369#note_3322243469_
<!-- STATUS NOTE END -->
epic