## Closing summary The API reference site ([api.gitlab.com/rest/](https://api.gitlab.com/rest/)) was able to render only 1 spec (GitLab's). This work allowed it to show multiple ones, by simply adding a single config entry. It now shows 2 (GitLab's and Artifact Central's)! ## Problem The interactive REST reference renders exactly one document. `src/config/scalar.js` passes Scalar a single `url:`, not a `sources:` array, so no document selector exists — the only switcher is an English/Japanese toggle over the same spec. No other service's spec can appear there, so every modular feature's API is invisible regardless of whether it has a spec. When a modular feature does publish a spec, there is nowhere to put it. ## Goal Adopt Scalar's `sources:` so the interactive reference can render and select between multiple specs, and so adding a component's spec becomes a matter of convention rather than per-service work. ## Technical considerations - The installed `@scalar/api-reference` 1.60.0 already supports `sources:`; it has not been adopted. - The interactive REST reference's shell is 1,853 bytes and fetches its spec lazily, so a document selector does not imply loading every spec up front. ## Links Interactive REST reference: https://api.gitlab.com/rest/ Reference source: https://gitlab.com/gitlab-com/gl-infra/api-docs <!-- STATUS NOTE START --> ## Status 2026-10-01 Work on this epic has been completed, closing it off! :clock1: **total hours spent this week by all contributors**: 4 :status: **TL;DR**: Epic is closed. :tada: **achievements**: * The API reference site ([api.gitlab.com/rest/](https://api.gitlab.com/rest/)) can now show more than one API spec, and now shows 2 (GitLab's and Artifact Central's)! This can be easily done by just adding a single config entry :issue-blocked: **blockers**: * :arrow_forward: **next**: * _Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/433#note_3934204430_ <!-- STATUS NOTE END -->