/v1/redoc

ReDoc over the same document — one scrollable reference page rather than a request console.

GET https://data.vike.io/v1/redoc

ReDoc over the same document: one scrollable reference page rather than a request console. Prefer it for reading, /v1/docs for calling.

No parameters. Serves text/html.

A live call and what it returned, captured 2026-09-03.

cURL

curl -H "X-API-KEY: $VIKE_API_KEY" https://data.vike.io/v1/redoc

200, 900 bytes — text/html, not JSON, so it is shown as the HTML it is. This is the complete body, verbatim; nothing is elided.

Example response


    <!DOCTYPE html>
    <html>
    <head>
    <title>vike.io Data API - ReDoc</title>
    <!-- needed for adaptive design -->
    <meta charset="utf-8"/>
    <meta name="viewport" content="width=device-width, initial-scale=1">
    
    <link href="https://fonts.googleapis.com/css?family=Montserrat:300,400,700|Roboto:300,400,700" rel="stylesheet">
    
    <link rel="shortcut icon" href="https://fastapi.tiangolo.com/img/favicon.png">
    <!--
    ReDoc doesn't change outer page styles
    -->
    <style>
      body {
        margin: 0;
        padding: 0;
      }
    </style>
    </head>
    <body>
    <noscript>
        ReDoc requires Javascript to function. Please enable it to browse the documentation.
    </noscript>
    <redoc spec-url="/v1/openapi.json"></redoc>
    <script src="https://cdn.jsdelivr.net/npm/redoc@2/bundles/redoc.standalone.js"> </script>
    </body>
    </html>

The served bytes are the thinnest of the three surfaces — 118 bytes less than /v1/docs — and they carry the reading-versus-calling split in a single element.

<redoc spec-url="/v1/openapi.json"> is the entire application: no Authorize dialog, no oauth2RedirectUrl, no request console, nothing that could submit a call. That is the difference between this page and Swagger UI stated in markup rather than in prose.

spec-url is host-relative, exactly as on /v1/docs, so the same consequence follows: the browser issues a second request to data.vike.io for the spec, and that request is behind the same header-only gate and carries no X-API-KEY of its own. Rendering this HTML is not enough on its own.

Note also the <noscript> line in the body: ReDoc renders nothing without JavaScript, so curl alone can never show you the reference — the 900 bytes above are all a non-browser client will ever receive. To read the surface from a terminal, fetch /v1/openapi.json instead.

ReDoc was the one surface left at the framework default when the other two moved under /v1/. It joined them on 2026-09-02, in the change that also added the security schemes.

What the document declares, what it leaves out, and the gate in front of it: Schema and spec.