Skip to main content
ApiGlow v0.3.0
EN
Copy page

Build the whole thing here.

Four stations, one configuration. Pick your schema, brand the app with a theme you author on the spot, decide what it does, fill in what the schema cannot say — and take the finished install away as two tags, a JSON block, a stylesheet or a prompt.

Nothing is sent anywhere. The page assembles the config in your browser, keeps your draft in this browser alone, and the preview hands its config to the next tab rather than to a server.

Point it at your API

The one key a config cannot do without, and the names that go around it.

Your browser fetches the schema, from here. Nothing about it reaches this site.

Name and logo
What to leave out

Patterns removing operations from the nav, the search and the exports: a tag, a method and path, an operationId. Documentation hiding, not access control — the browser still downloads the whole schema.

openapi.overlays

OpenAPI Overlay 1.1 documents applied to the schema at load, in declaration order.

Make it yours

A daisyUI theme is a block of custom properties, which is why the app takes yours at runtime — no build step, nothing to compile.

No theme yet. Start from any of the 37 the app ships with, change one color, and the rest follows.

What the reader is offered
theme.available
The entries in the theme selector. All 37 are bundled, so listing one costs nothing.
language.available

Decide what it does

Every switch below is off the default only if you move it, and only then does it reach the config.

features
tryIt
history

Whichever threshold is reached first purges the request history.

Crawlers and control

Fill the docs

Everything the schema cannot say: your environments, your guides, your notices, your scenarios.

environments

Pre-filled on first load. After that the reader's own storage is authoritative.

docsPages

Your prose pages, woven into the nav next to the reference.

announcements

A strip above the header. Inline Markdown; a window of dates publishes and retires it on its own.

scenarios

Scenarios shipped with the docs, pointing at exported files. In a multi-spec install they belong on the API entries instead.

oauth and feedback

The public client id of an OAuth2 scheme, keyed by its name in securitySchemes. Never a client secret — the host page is public.