Integration & APIs

OpenAPI linter

Lint an OpenAPI 3.x spec for the things that break downstream — missing operationIds, undeclared path parameters, operations with no success response.

OpenAPI document (YAML or JSON)

openapi: 3.0.3
info:
  title: Orders API
  version: 1.2.0
servers:
  - url: https://api.example.com/v1
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
  schemas:
    Order:
      type: object
      properties:
        id: { type: string }
security:
  - bearerAuth: []
paths:
  /orders:
    get:
      operationId: listOrders
      summary: List orders
      tags: [orders]
      responses:
        '200': { description: OK }
    post:
      summary: Create an order
      tags: [orders]
      requestBody:
        content:
          application/json:
            schema: { $ref: '#/components/schemas/Order' }
      responses:
        '201': { description: Created }
  /orders/{orderId}:
    get:
      operationId: listOrders
      summary: Get one order
      tags: [orders]
      responses:
        '200': { description: OK }
  /orders/{orderId}/cancel:
    post:
      operationId: cancelOrder
      parameters:
        - name: orderId
          in: path
          required: true
          schema: { type: string }
      responses:
        '409': { description: Already shipped }

A linter rather than a renderer — editors already show you the endpoints. These checks catch what actually causes trouble downstream: missing operationId (every generated SDK method renames itself when a path changes), duplicate IDs, path templates with no matching parameter, and operations with no success response. YAML and JSON both accepted. Runs in your browser.

Other tools

These exist because the underlying problem is real. If the numbers you just put in look uncomfortable, that is usually worth a conversation.

Tell us what you're running