DXS OpenAPI Swaggerizer
Automatically detect supported OpenAPI and Swagger JSON documents on public sites, localhost, and private networks. Browse structured documentation in the page and test OpenAPI 3.0/3.1 operations from a separate extension tab.
Current Status
Visual documentation for OpenAPI 3.0/3.1 and Swagger 2.0, with operation testing for OpenAPI 3.0/3.1.
Checks supported JSON specifications displayed on HTTP and HTTPS pages, including dynamic URLs that do not end in .json.
Groups endpoints by tags, root paths, and sub-resources, with a sticky sidebar for moving between tags.
Explore methods, paths, operation IDs, summaries, descriptions, and declared responses.
In a separate tab, select the server, parameters, supported authentication, and request body; inspect the response status, headers, and body. Swagger 2.0 is for visual documentation only.
Features
Turn a flat list of routes into a navigable reference, then open the tester when you need to send an OpenAPI 3.0/3.1 request.
Detects supported specifications on public sites, localhost, and private networks.
Looks at rendered page content; the URL does not need a particular filename or extension.
Specifications larger than 25 Mi characters are skipped.
Built with vanilla JavaScript and no third-party runtime libraries.
Technical
Specification detection and visual rendering happen locally. A test request is sent only after you choose Send request in the separate tester tab.
The content script can run on HTTP and HTTPS pages across sites, including localhost and private networks, to detect supported JSON. It does not run on file:// or browser-internal pages.
When you choose Send request, the extension requests optional access to the selected API origin and sends the request directly to that server.
The selected API server and optional environment settings use Chrome local storage; the language preference uses Chrome Sync. The selected specification and operation are held temporarily in a one-time local session.
Endpoint Exploration
Challenge
Raw JSON makes it hard to scan operations and understand structure quickly.
Delivery
The interface reorganizes endpoints, methods, and usage context into a more navigable view.
Operation Details
Challenge
A flat JSON document makes parameters and declared responses hard to find.
Delivery
The visual documentation places each operation's parameters and declared responses near its method and path.
Security
The extension reads candidate page content locally and asks for access to an API origin only when you send a test request.
Specifications are detected and rendered in your browser, without upload to DXS servers.
The URL, parameters, body, and credentials you enter go directly to the selected API server only after you choose Send request.
Credentials remain in the tester tab memory and are not saved through chrome.storage. Browser cookies are not sent with test requests.
Specifications and test data are not sent to DXS servers or analytics services.
Privacy
Interface settings are stored locally, and the language preference uses Chrome Sync. A one-time local session passes the selected specification and operation to the tester. Credentials, request bodies, and responses are not saved through chrome.storage.
01
The content script examines candidate HTTP and HTTPS page content in your browser.
02
Only a request you choose to send goes directly to the selected API server; browser cookies are not included.
Settings
The selected API server and optional environment settings are stored locally; the interface language uses Chrome Sync. The extension does not send these preferences to DXS or analytics.
Known Limits
OpenAPI 3.0 and 3.1 support visual documentation and operation testing. Swagger 2.0 supports visual documentation only. Documents larger than 25 Mi characters are skipped, and automatic detection applies to HTTP and HTTPS pages.
Add the extension from the Chrome Web Store using the official link.
Open a page displaying supported OpenAPI or Swagger JSON on a public site, localhost, or a private network. The URL can be a dynamic route.
Use the grouped routes and sticky sidebar to inspect operations and declared responses.
For OpenAPI 3.0/3.1, open the separate tester tab, review the request, and choose Send request to contact the selected API server.
Check that it displays a valid OpenAPI 3.0/3.1 or Swagger 2.0 JSON specification on an HTTP or HTTPS page. Documents larger than 25 Mi characters are skipped.
Automatic detection requires the content script on HTTP and HTTPS pages across sites, including localhost and private networks. It examines candidate content locally and cannot access file:// or browser-internal pages.
Swagger 2.0 specifications are available for visual documentation. Operation testing is supported for OpenAPI 3.0 and 3.1.
Only after you choose Send request. The extension requests optional access to the selected API origin and sends your URL, parameters, body, and entered credentials directly to that API server.
No. Credentials stay in the tester tab memory; credentials, request bodies, and responses are not saved through chrome.storage. Browser cookies are not sent with test requests.
The selected API server and optional environment settings use Chrome local storage; the language preference uses Chrome Sync. The selected specification and operation are held temporarily in a one-time local session.
Yes. Automatic detection covers supported JSON displayed on HTTP and HTTPS pages, including localhost and private networks.
For bug reports or support, contact DATAXSTUDIOS directly: contato@dataxstudios.com.br
Legal
This extension is an independent tool and is not affiliated with, endorsed by, or sponsored by SmartBear Software (Swagger) or the OpenAPI Initiative. © 2026 DXS - DATAXSTUDIOS. All rights reserved. For support or bug reports: contato@dataxstudios.com.br
