Does it fetch my specification from a URL?

No. The document is read as text in the page, and a reference to another file is shown as a reference rather than followed. That keeps the page working offline and keeps a private spec private.

Which versions are supported?

OpenAPI 3.0 and 3.1 as well as Swagger 2.0. The overview writes down which one it found, and a Swagger 2 document's host, basePath and schemes are shown as the server.

How deep does a schema go?

Nested objects are expanded a couple of levels and then summarised as object, so one schema cannot flood the page. The shape is still clear, and the full definition is in the document you pasted.

OpenAPI Viewer

Specification

openapi: 3.0.3
info:
  title: Orders API
  version: 1.2.0
  description: Manage orders and their line items.
servers:
  - url: https://api.example.com/v1
paths:
  /orders:
    get:
      summary: List orders
      tags: [Orders]
      parameters:
        - name: status
          in: query
          description: Only return orders in this state.
          schema:
            type: string
            enum: [open, shipped, cancelled]
        - name: limit
          in: query
          schema:
            type: integer
            default: 20
      responses:
        '200':
          description: A page of orders
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Order'
    post:
      summary: Create an order
      tags: [Orders]
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Order'
      responses:
        '201':
          description: The order was created
  /orders/{id}:
    get:
      summary: Fetch one order
      tags: [Orders]
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: The order
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Order'
        '404':
          description: No such order
components:
  schemas:
    Order:
      type: object
      required: [id, status]
      properties:
        id:
          type: string
        status:
          type: string
          enum: [open, shipped, cancelled]
        total:
          type: number
          format: double

Format File

Swagger 2.0 and OpenAPI 3 documents are both accepted. Nothing is fetched: references are resolved inside the document you paste, so a spec split across several files is out of scope here.

About this tool

Paste an OpenAPI or Swagger document and read it as a list of operations rather than as a wall of YAML. Each endpoint shows its method, its parameters, its request body and the responses it can return, with references resolved so a schema appears where it is used.

Questions

Does it fetch my specification from a URL?: No. The document is read as text in the page, and a reference to another file is shown as a reference rather than followed. That keeps the page working offline and keeps a private spec private.
Which versions are supported?: OpenAPI 3.0 and 3.1 as well as Swagger 2.0. The overview writes down which one it found, and a Swagger 2 document's host, basePath and schemes are shown as the server.
How deep does a schema go?: Nested objects are expanded a couple of levels and then summarised as object, so one schema cannot flood the page. The shape is still clear, and the full definition is in the document you pasted.

OpenAPI Viewer

OpenAPI Viewer

Overview

Operations

History for this tool

About this tool

Questions