#282 · Developer Tool

OpenAPI Operation ID Checker

Audit operationId values before an OpenAPI document reaches an SDK generator. The checker finds missing IDs, duplicate IDs, whitespace, and identifiers that are awkward for common code generators. Every issue points back to its HTTP method and path, while valid operations remain counted in the summary. It does not invent replacements, because naming conventions belong to the API team, but the report is specific enough to fix the source document without searching through the entire paths tree.

Developer Input

OpenAPI JSON
Ad space

How to use this developer tool

  1. Paste a JSON-formatted API document or load the included sample.
  2. Check that the document shape matches the label above the editor.
  3. Select “Check Operation IDs” or press Ctrl/Cmd + Enter.
  4. Review the summary and download the copy-ready result.

What this developer tool does

Each HTTP operation is checked for presence, uniqueness, and a conservative identifier pattern suitable for generated method names.

An accepted ID begins with a letter or underscore and continues with letters, numbers, underscores, dots, or hyphens. Duplicate checks are case-sensitive.

A clean result means the local identifier rules passed; it is not a full OpenAPI validation.

Example

The Sample button loads a small specification chosen for this operation. Running it produces the same structured fields shown in the output panel.

{
  "openapi": "3.0.3",
  "info": {
    "title": "Orders",
    "version": "1"
  },
  "paths": {
    "/orders": {
      "get": {
        "operationId": "listOrders",
        "responses": {}
      },
      "post": {
        "operationId": "listOrders",
        "responses": {}
      }
    },
    "/orders/{id}": {
      "get": {
        "responses": {}
      }
    }
  }
}

Use cases

  • Review an API contract during a pull request.
  • Prepare documentation or deterministic test fixtures.
  • Find migration work before changing generators or clients.
  • Export a focused report without sharing the source document.

Tips for reliable output

  • Bundle remote references before running the page.
  • Keep operation IDs stable across published versions.
  • Prefer explicit examples for domain-specific values.
  • Validate the complete document after applying generated output.
  • Commit the original specification before a conversion.

Processing details

The checker builds an index of operationId values, records every location, then emits missing, invalid, and duplicate findings in path order.

Generator-specific reserved words are not checked. External references and YAML input are outside this browser-only audit.

Frequently asked questions

Does this page accept YAML OpenAPI files?

No. This browser-only implementation accepts JSON so parsing behavior stays predictable without loading an external YAML library. Convert YAML to JSON first.

Are external $ref URLs resolved?

No. Local JSON Pointer references are handled where the operation needs them, but remote references are not fetched.

Does the result replace a full OpenAPI validator?

No. OpenAPI Operation ID Checker performs its documented transformation or audit. Use a standards-aware validator before publishing a specification.

Is the specification uploaded to a server?

No. Processing runs in the current browser tab. The page does not send the pasted document to an API.

Can I download the result?

Yes. Run the tool, then use Download for the primary output or the JSON and CSV buttons when those structured exports are available.

Input contract

ItemRequirement
FormatJSON object
ExecutionLocal browser
Remote refsNot fetched

API & GraphQL Tools

Browse contract inspection, conversion, request, response, and schema utilities.

Open category hub