Developer platforms
Public API reference that matches your product rather than a generic docs theme.
Product interface templateDeveloper Platform
API Documentation React Template
A documentation interface for developer platforms: endpoint index, schema tables, response matrix and a sandbox that runs.
- Template
- API Reference
- Type
- Product interface
- In kit
- 07 / 11
02Overview
What the API Documentation React Template gives you.
This is the KRENOS API documentation React template — a signed-in style reference interface rather than a marketing page. It has the three-column shape developers expect: an endpoint index on the left, specification in the middle, and a dark SDK client on the right.
It is the right starting point when your documentation is the product surface, and generic docs themes do not match the rest of your application.
03Key features
Built around what this template actually does.
- 01
Endpoint index with command-palette filter
Grouped endpoints with method badges and per-group counters, filtered from a search field with a keyboard shortcut.
- 02
Request and schema tables
Request headers with required flags, a body schema with types and descriptions, and an HTTP response matrix with status tones.
- 03
Interactive SDK sandbox
A client panel that runs a request and reports console response telemetry — status and execution duration — through idle, running, success and error states.
- 04
Specification breadcrumb
Semantic breadcrumb navigation through the protocol version and the current endpoint.
04What's inside
7 sections, in page order.
Every one is a working part of the live template, not a screenshot. Open the demo to use them.
- 01
Specification header
Protocol version, breadcrumb and status.
- 02
Endpoint index
Grouped, filterable navigation with method badges.
- 03
Request headers
A typed table with required indicators.
- 04
Body schema
Field names, types and descriptions.
- 05
Response matrix
Status codes with tone-coded variants and per-status schemas.
- 06
SDK client
The interactive sandbox with response telemetry.
- 07
Support panel
A closing block for private peering or contact.
05Who it's for
Products this direction suits.
Internal API portals
Service catalogues and schema references for platform teams.
SDK-first products
Documentation where a runnable example is the fastest path to activation.
06Technology & customization
The stack underneath.
- Endpoints, schemas and responses are typed data structures
- Accessible tab, table and search patterns
- Keyboard shortcut handling for the endpoint filter
- Syntax-highlighted snippets rendered without a highlighting dependency
What you can change
- Describe your own API by editing `src/data/apiReference.ts` — the interface regenerates.
- Snippets per language live in `src/data/apiSnippets.ts`.
- Method badge colours map to shared semantic tokens.
- The sandbox can be pointed at a real endpoint.
Frontend only
The sandbox does not call an API. It advances through typed response fixtures on a timer, so the documented endpoints, keys and hosts are deliberately fake (`kr_demo_…`, `*.example`).
07Questions
Frequently asked.
Not out of the box. Endpoints and schemas are typed TypeScript data. You can populate that data from an OpenAPI document at build time, but no parser is included.
Yes. Replace the simulated run with a fetch to your endpoint — the idle, running, success and error states already exist.
Yes. The filter has a keyboard shortcut, and the index is fully operable with the keyboard with visible focus throughout.
No. It is a documentation and reference interface. For operational dashboards the kit includes observability, governance and vault templates.
08Related templates
Others in the kit worth comparing.
Every KRENOS purchase includes all eleven, so these are alternatives to consider, not add-ons.
KRENOS · API Reference
See it running. Then make it yours.
The demo is the real template, not a video. It opens with a thin KRENOS bar so you can switch templates, preview it at phone, tablet and desktop widths, or come back to the explorer.