redoc definition

Github openAPI definition

OpenAPI/Swagger-generated API Reference Documentation.

This is README for ``2.0`` version of ReDoc (React based). README for ``1.x`` version is on the branch `v1.x <>`__

ReDoc demo

ReDoc demo


  • Extremely easy deployment

  • redoc-cli with ability to bundle your docs into zero-dependency HTML file

  • Server Side Rendering ready

  • The widest OpenAPI v2.0 features support (yes, it supports even discriminator) image10

  • OpenAPI 3.0 support

  • Neat interactive documentation for nested objects

  • Code samples support (via vendor extension)

  • Responsive three-panel design with menu/scrolling synchronization

  • Integrate API Introduction into side menu - ReDoc takes advantage of markdown headings from OpenAPI description field. It pulls them into side menu and also supports deep linking.

  • High-level grouping in side-menu via `x-tagGroups <docs/>`__ vendor extension

  • Simple integration with create-react-app (sample)

  • Branding/customizations via `theme option <#redoc-options-object>`__


  • [x] [STRIKEOUT:OpenAPI v3.0 support]

  • [x] [STRIKEOUT:performance optimizations]

  • [x] [STRIKEOUT:better navigation (menu improvements + search)]

  • [x] [STRIKEOUT:React rewrite]

  • [x] [STRIKEOUT:docs pre-rendering (performance and SEO)]

  • [ ] ability to simple branding/styling

  • [ ] built-in API Console


Important: all the 2.x releases are deployed to npm and can be used via jsdeliver: - particular release, e.g. v2.0.0-alpha.15: - next release:

Additionally, all the 1.x releases are hosted on our GitHub Pages-based CDN: - particular release, e.g. v1.2.0: - v1.x.x release: - latest release: - it will point to latest 1.x.x release since 2.x releases are not hosted on this CDN but on unpkg.

Version Guidance

ReDoc Release

OpenAPI Specification


3.0, 2.0









<!DOCTYPE html>
    <!-- needed for adaptive design -->
    <meta charset="utf-8"/>
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <link href=",400,700|Roboto:300,400,700" rel="stylesheet">

    ReDoc doesn't change outer page styles
      body {
        margin: 0;
        padding: 0;
    <redoc spec-url=''></redoc>
    <script src=""> </script>

That’s all folks!

IMPORTANT NOTE: if you work with untrusted user spec, use untrusted-spec option to prevent XSS security risks.

1. Install ReDoc (skip this step for CDN)

Install using yarn:

yarn add redoc

or using npm:

npm install redoc --save

2. Reference redoc script in HTML

For CDN:

<script src=""> </script>

For npm:

<script src="node_modules/redoc/bundles/redoc.standalone.js"> </script>

3. Add <redoc> element to your page

<redoc spec-url="url/to/your/spec"></redoc>

4. Enjoy :smile:

Usage as a React component

Install peer dependencies required by ReDoc if you don’t have them installed already:

npm i react react-dom mobx@^4.2.0 styled-components

Import RedocStandalone component from ‘redoc’ module:

import { RedocStandalone } from 'redoc';

and use it somewhere in your component:

<RedocStandalone specUrl="url/to/your/spec"/>


<RedocStandalone spec={/* spec as an object */}/>

Also you can pass options:

    nativeScrollbars: true,
    theme: { colors: { primary { main: '#dd5522' } } },

Here are detailed options docs.

You can also specify onLoaded callback which will be called each time Redoc has been fully rendered or when error occurs (with an error as the first argument). NOTE: It may be called multiply times if you change component properties

  onLoaded={error => {
    if (!error) {

The Docker way

ReDoc is available as pre-built Docker image in official Docker Hub repository. You may simply pull & run it:

docker pull redocly/redoc
docker run -p 8080:80 redocly/redoc

Also you may rewrite some predefined environment variables defined in Dockerfile. By default ReDoc starts with demo Petstore spec located at, but you may change this URL using environment variable SPEC_URL:

docker run -p 8080:80 -e SPEC_URL= redocly/redoc


Security Definition location

You can inject Security Definitions widget into any place of your specification description. Check out details here.

Swagger vendor extensions

ReDoc makes use of the following vendor extensions: * `x-logo <docs/>`__ - is used to specify API logo * `x-traitTag <docs/>`__ - useful for handling out common things like Pagination, Rate-Limits, etc * `x-code-samples <docs/>`__ - specify operation code samples * `x-examples <docs/>`__ - specify JSON example for requests * `x-nullable <docs/>`__ - mark schema param as a nullable * `x-displayName <docs/>`__ - specify human-friendly names for the menu categories * `x-tagGroups <docs/>`__ - group tags by categories in the side menu * `x-servers <docs/>`__ - ability to specify different servers for API (backported from OpenAPI 3.0) * `x-ignoredHeaderParameters <docs/>`__ - ability to specify header parameter names to ignore

<redoc> options object

You can use all of the following options with standalone version on tag by kebab-casing them, e.g. scrollYOffset becomes scroll-y-offset and expandResponses becomes expand-responses.

  • untrustedSpec - if set, the spec is considered untrusted and all HTML/markdown is sanitized to prevent XSS. Disabled by default for performance reasons. Enable this option if you work with untrusted user data!

  • scrollYOffset - If set, specifies a vertical scroll-offset. This is often useful when there are fixed positioned elements at the top of the page, such as navbars, headers etc; scrollYOffset can be specified in various ways:

  • number: A fixed number of pixels to be used as offset;

  • selector: selector of the element to be used for specifying the offset. The distance from the top of the page to the element’s bottom will be used as offset;

  • function: A getter function. Must return a number representing the offset (in pixels);

  • suppressWarnings - if set, warnings are not rendered at the top of documentation (they still are logged to the console).

  • lazyRendering - Not implemented yet [STRIKEOUT:if set, enables lazy rendering mode in ReDoc. This mode is useful for APIs with big number of operations (e.g. > 50). In this mode ReDoc shows initial screen ASAP and then renders the rest operations asynchronously while showing progress bar on the top. Check out the demo for the example.]

  • hideHostname - if set, the protocol and hostname is not shown in the operation definition.

  • expandResponses - specify which responses to expand by default by response codes. Values should be passed as comma-separated list without spaces e.g. expandResponses="200,201". Special value "all" expands all responses by default. Be careful: this option can slow-down documentation rendering time.

  • requiredPropsFirst - show required properties first ordered in the same order as in required array.

  • sortPropsAlphabetically - sort properties alphabetically

  • showExtensions - show vendor extensions (“x-” fields). Extensions used by ReDoc are ignored. Can be boolean or an array of string with names of extensions to display

  • noAutoAuth - do not inject Authentication section automatically

  • pathInMiddlePanel - show path link and HTTP verb in the middle panel instead of the right one

  • hideLoading - do not show loading animation. Useful for small docs

  • nativeScrollbars - use native scrollbar for sidemenu instead of perfect-scroll (scrolling performance optimization for big specs)

  • hideDownloadButton - do not show “Download” spec button. THIS DOESN’T MAKE YOUR SPEC PRIVATE, it just hides the button.

  • disableSearch - disable search indexing and search box

  • onlyRequiredInSamples - shows only required fields in request samples.

  • theme - ReDoc theme. Not documented yet. For details check source code: theme.ts

Advanced usage of standalone version

Instead of adding spec-url attribute to the <redoc> element you can initialize ReDoc via globally exposed Redoc object:

Redoc.init(specOrSpecUrl, options, element, callback?)
  • specOrSpecUrl is either JSON object with specification or an URL to the spec in JSON or YAML format

  • options options object

  • element DOM element to put ReDoc into

  • callback (optional) - callback to be called after Redoc has been fully rendered. It is also called also on errors with error as the first argument

Redoc.init('', {
  scrollYOffset: 50
}, document.getElementById('redoc-container'))