Nobuf

OpenAPI Editor & Contract Tester

Local only

Design, validate, document, mock, generate code, and compare OpenAPI contracts locally.

OpenAPI contract
openapi: 3.2.0
info:
  title: Pocket Tasks API
  version: 1.0.0
  description: A compact example for designing and reviewing an API contract.
servers:
  - url: https://api.example.com/v1
paths:
  /tasks:
    get:
      operationId: listTasks
      summary: List tasks
      tags: [Tasks]
      parameters:
        - name: limit
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 20
      responses:
        "200":
          description: Task collection
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: "#/components/schemas/Task"
    post:
      operationId: createTask
      summary: Create a task
      tags: [Tasks]
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: "#/components/schemas/NewTask"
      responses:
        "201":
          description: Task created
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Task"
  /tasks/{taskId}:
    get:
      operationId: getTask
      summary: Get a task
      tags: [Tasks]
      parameters:
        - name: taskId
          in: path
          required: true
          schema: { type: string, format: uuid }
      responses:
        "200":
          description: Task found
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Task"
        "404":
          description: Task not found
components:
  schemas:
    NewTask:
      type: object
      required: [title]
      properties:
        title: { type: string, example: Ship the release }
        done: { type: boolean, default: false }
    Task:
      allOf:
        - $ref: "#/components/schemas/NewTask"
        - type: object
          required: [id]
          properties:
            id: { type: string, format: uuid }
            createdAt: { type: string, format: date-time }

How to use it

  1. 01

    Open a contract

    Paste or import an OpenAPI YAML or JSON document, switch formats, and run structural and reference diagnostics.

  2. 02

    Explore and test the design

    Browse operations, parameters and responses, generate schema-based mock payloads, and copy cURL, Fetch, or Python examples.

  3. 03

    Review compatibility

    Compare a candidate contract with the current version and identify removed operations, responses, and newly required parameters before release.

Frequently asked questions

Which OpenAPI versions are supported?

The editor understands OpenAPI 3.0, 3.1, and 3.2 structures. Swagger 2.0 can be inspected with a migration warning.

Does it call my API or fetch external references?

No. Code and mock payloads are generated locally. External $ref URLs are reported but never fetched automatically.

Is this a complete official conformance validator?

No. It provides practical structural, operation, path-parameter, response, and reference checks. The OpenAPI specification remains authoritative.

Does the diff prove backward compatibility?

No. It flags high-value structural changes conservatively; production compatibility also depends on schemas, semantics, clients, security, and runtime tests.

Keep working with other focused browser utilities.

All tools

Local by default; remote data sources are clearly disclosed.

© 2026 Nobuf

Nobuf

Fast, local-first utilities powered by your browser.