v1.8.7: Branded API reference with working try-it
Swagger UI is gone. In its place, an API Reference page in the dashboard rendering Scalar, branded to match the app, with working try-it against the signed-in user's own organization.
Full notes: 1.8.7 on GitHub.
Where to see it
/ApiReference in your dashboard, where try-it is live against your own organization. The same reference is published statically at docs.snapcd.io/api-reference for reading without an account — there is no server behind that one, so the try-it affordances are hidden.
What changed
Swashbuckle is removed entirely. The built-in ASP.NET Core generator emits OpenAPI 3.1 at /openapi/v1.json, titled "Snap CD API" and versioned with the actual server release rather than a placeholder. Scalar is just the renderer.
Scalar expects to control window scrolling, position popovers in document coordinates, and stamp theme classes on <body>, so it runs on a standalone page that we author — theme cookie stamped server-side, snapcd-theme.css, the vendored bundle — which the dashboard page frames.
Try-it that works
Authorization-code + PKCE via a seeded client: a signed-in user authorizes silently and try-it calls run with a real token. Clicking any "Authentication required" badge triggers the flow directly.
The OpenAPI document is generated per request, so the caller's current organization is stamped as the example on every {organizationId} parameter — try-it and the generated code samples are prefilled with the org you are actually working in.
Branding and vendoring
Scalar's theme variables are mapped onto the Snap CD tokens, so light and dark follow the rest of the app. @scalar/api-reference is committed under wwwroot/scalar/ rather than loaded from a CDN.
Intelligent GitOps for Infrastructure as Code. Automate, orchestrate, and scale your infrastructure deployments with confidence.
© 2026 Snap CD. All rights reserved.