Webhook HMAC Signer
Sign and verify GitHub, Stripe, and Slack webhook signatures locally.
OpenCheck a spec, see its endpoints, generate types and catch breaking changes in one place.
YAML or JSON specs both work offline-first.
Validate paths and pick an operation for examples.
Export interfaces from components.schemas.
Highlight breaking vs additive API changes.
A backend pull request changes the orders API spec, and you need to know whether the mobile app will break before it merges. Pasting the old and new specs side by side lists what was removed or tightened, and gives you fresh TypeScript types for the new version.
Paste an OpenAPI 3.x document as JSON or YAML. For YAML the page loads the js-yaml library from a CDN on first use and falls back to a built-in reader if that fails. The validation checklist covers the openapi version, the info block, paths and path templating, operationId values and response coverage, and rolls them into a score. Every operation is listed with its method, path, summary, parameter count, request body and response codes. Pick one from the dropdown to get an example HTTP request and a cURL command built from the examples and defaults in the spec.
TypeScript interfaces are generated from components.schemas, including enums and $ref links, and can be copied or downloaded as a .d.ts file. Paste a second version into the compare box for a diff that separates breaking changes from additive ones. It works at the level of operations, parameters, request bodies and response codes, so a property changing type inside a schema is not caught. Swagger 2.0 documents are detected and flagged rather than analyzed. For a quick Postman import, the lighter OpenAPI to Postman converter is enough, and runtime validators from a schema cover Zod, TypeBox and Valibot.
Parsing and analysis happen locally; the optional js-yaml download is the only network request.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
No. External references to other files are not fetched. Bundle the spec into a single document first, then paste it.
From the example and default values declared on your parameters and schemas. Where none exist, the tool uses a placeholder based on the type or format, such as an example email address for an email field.
Removing an operation, adding a required parameter or making an existing one required, removing a 2xx response, adding, removing or requiring a request body, and renaming an operationId. Removed parameters, new responses and deprecations are listed as non-breaking.