andrewwalsh / openapi-devtools Goto Github PK

It would be awesome to have this in Firefox as well :-)

Excellent tool, congrats for hn # 1!

Would it be possible to opt-in always running the extension on the background, so that you don't need to worry about profiling a specific website, and just passively collect all API's you've accessed?

Might be relevant when you've lost access to a front (or if the front gets taken down) and you'd like to directly communicate with the API.

Currently, closing the browser results in a loss of the generated OpenAPI specification data. To enhance usability and continuity, could we consider the following features?

1. Implementing a session save feature that allows users to pause and resume their recording sessions at a later time.

2. Providing an option to upload a JSON file of a previously downloaded OpenAPI specification, enabling users to continue recording from where they left off.

Awesome work! I have one feature request though - could it record auth headers/tokens? This would be super useful for logging which requests require authorization and how to send an authorized request

It would be helpful to see what some possible values would be for each key in a JSON API instead of only the type of the value.

Suggested improvement to the ReadMe: add a paragraph explaining what an OpenAI specification is. I just read this:

https://swagger.io/specification/

...and I'm not quite sure yet what it is or where it is used.

I've used OpenAI a lot through its UI but not via code yet. :)

On Windows 11 running Chrome Version 119.0.6045.106 (Official Build) (64-bit)

This could be a misunderstanding on my part but my assumption is that post install, it would show either in this list.

or in this list

If there is something more to do in order to get it to show up it might be worth putting in the readme.

I left ideas in HN comments but leaving them here for posterity:

1. Ability to filter response properties.
2. Ability to work with non-JSON (web scraping) by defining a mapping of CSS selectors to response properties.
3. Cross-reference host names of captured requests with publicly documented APIs.
4. If auth headers are found, prompt the user for credentials that can then be stored locally.
5. "Repeater" functionality similar to the feature found in Burp Suite.
6. Generate clients on the fly based on the generated OpenAPI spec.
7. Train a machine learning model to recognize and extract tabular and repeated data based on training data.
8. Optionally publish generated OpenAPI specs to a central site or open PR to a GH repo, "awesome-openapi-devtools"?
9. Look for embedded data similar to what https://github.com/BishopFox/jsluice extracts and offer it as endpoints.

For some of these features, it may make sense to incorporate a server-side component. For example, sending captured data to be trained (7) or cross-referencing with existing documented APIs based on the host names (3).