Love the idea. I’m always finding myself writing little user scripts / browser extensions to extend websites I use all the time, and trying to use an API I found in the devtools network requests page always gets annoying when I have to try and do anything beyond replicating the exact input/output I found in the original request.
Haven’t fully looked through the features/docs, so forgive me if my question is answered in there, but what does support look like for:
- Exporting to Swagger/OpenAPI Spec
- Exporting to generated SDK (I know some tools exist that can generate SDKs from OpenAPI/Swagger, so maybe some of these tools have licenses that are compatible with your product?)
- Support for URL path variables (e.g. `/users/{user_id}`)
- Support for URL query parameters (and filtering for common “noise” parameters, e.g. Google analytics)
- Support for non-JSON input/output (e.g. an endpoint that accepts multipart form data)
Awesome idea though. I’m definitely going to try this out. Beautiful UI and website too. I’m stoked to play around with this!
I'm glad you like the idea! Let me answer your questions one by one:
- Exporting to Swagger/OpenAPI Spec: Currently, exporting to Swagger/OpenAPI isn't supported, but it's on my to-do list to look into. Right now, JavaScript code is the only export format.
- Exporting to a Generated SDK: Same as above. I'm considering integrating tools that can generate SDKs from OpenAPI/Swagger specs, so this might be included in a future update.
- Support for URL Path Variables (e.g., `/users/{user_id}`): Yes, API Parrot supports URL path variables!
- Support for URL Query Parameters (and filtering out common "noise" parameters like Google Analytics): Yes, API Parrot supports URL query parameters, and there are measures in place to filter out the noise.
- Support for Non-JSON Input/Output (e.g., endpoints that accept multipart form data): There is support for non-JSON input/output formats, but multipart form data isn't supported at this time. You can find all the supported data types on this page: https://docs.apiparrot.com/docs/tutorial-extras/exchange-mod...
Thanks again for your support! I'm excited for you to try it out, and I'd love to hear your feedback after you've had a chance to play around with it.
Haven’t fully looked through the features/docs, so forgive me if my question is answered in there, but what does support look like for:
- Exporting to Swagger/OpenAPI Spec
- Exporting to generated SDK (I know some tools exist that can generate SDKs from OpenAPI/Swagger, so maybe some of these tools have licenses that are compatible with your product?)
- Support for URL path variables (e.g. `/users/{user_id}`)
- Support for URL query parameters (and filtering for common “noise” parameters, e.g. Google analytics)
- Support for non-JSON input/output (e.g. an endpoint that accepts multipart form data)
Awesome idea though. I’m definitely going to try this out. Beautiful UI and website too. I’m stoked to play around with this!