scalar

You can replace Swagger UI with Scalar by mapping Scalar API references using MapScalarApiReference alongside MapOpenApi, configuring custom routes like /scalar/v1, and applying environment guards to expose endpoints securely during development.

To secure Scalar Try It calls in production, disable the external proxy by configuring WithProxy(null) and require authorization on the documentation endpoints using .RequireAuthorization to prevent leaking internal API structure.

Yes, you can configure authentication prefill in Scalar by defining security schemes within your OpenAPI document, which Scalar then uses to render the authentication UI strictly based on those defined schemes.

Scalar supports multiple OpenAPI documents in a .NET application by utilizing MapOpenApi and MapScalarApiReference mappings, allowing you to serve distinct interactive documentation endpoints for different API segments.

The best way to prevent unauthorized access to interactive API docs in production is to apply .RequireAuthorization to the Scalar endpoints, ensuring the API documentation routes are protected while remaining available in development environments.

You should disable the Scalar external proxy with WithProxy(null) when exposing sensitive APIs to prevent unauthorized external Try It calls from executing against your production endpoints through the documentation interface.