<p>For years, editor.swagger.io was the place everyone went to sketch out an OpenAPI definition. It was familiar, convenient, and good enough for its time. The problem is simple though: the specification has moved on, tooling expectations have moved on, and that classic editor has not kept pace.</p><p>If you work with OpenAPI today especially with the changes landing in 3.2 you need more than syntax colouring. You need proper linting. You need awareness of the latest features. You need a clear structure of your document so you can navigate without hunting through thousands of lines.</p><p>So we built it.</p><h3 id="a-modern-editor-for-openapi-3-2">A Modern Editor for OpenAPI 3.2</h3><p>The new API editor at app.developerhub.io/api-editor is designed to be the natural successor to Swagger Editor. It is fully free to use, and you do not need an account.</p><p>Here is what it brings to the table:</p><p>Full OpenAPI 3.2 support</p><p>Every new feature in 3.2 works out of the box. Structured tags, QUERY, updated XML modelling, improved multipart definitions, event streams and more. No hacks or extensions to make the editor understand your document.</p><p>Built in linting</p><p>The editor flags issues as you type, from simple mistakes to deeper design concerns. You get instant feedback, not silent failures.</p>