Hi @bhav15h, saving response along with the request seems like an handy feature. We'll consider implementing this on a later stage. If anyone wants to contribute to this feature request, feel free to pick it up.

Hi, this seems interesting, mind if I look into it?

@sguzmanm yes, feel free to pick this up.

Hi @liyasthomas I've been having a hard time trying to work on the issue since I see it's too big, would you mind looking at the linked PR for further guidance?

Is your feature request related to a problem? Please describe. I would like to be able to save an API response similar to the feature in postman.

1. This will then allow us to preview the API instead of having to do a request to get the response.
2. Also this is helpful whereby if you use a token to authenticate and the token has expired, instead of reauthenticate to view a response you get to quickly see the structure and response of the API.

Describe the solution you'd like The solution for this is when a request to an API has returned a result we have a new button to save the response. This would be nested under the saved API request. We should be able to rename the saved response as there could be different responses from 1 request. e.g if an exception was raised in the api we could receive a different response.

Describe alternatives you've considered At the moment the only alternative is to save the response in a file locally, but this is very hectic and not easily sharable to other people in the team as we may have a long list of 100 APIs.

Additional context Postman seem to have done it very well.

Hey @liyasthomas, are there plans to add this feature anytime soon?

+1 for this feature. Postman has the ability to save an API response as an "example" under requests in a collection.

This is something we have debated a lot on whether or not to implement, even had the PR in. But what we think is "Examples" as a thing within requests are more of a documentation thing and not exactly a "Testing" thing.

We are really vary and careful with the things we want to the REST Testing pages because we do not want to build Hoppscotch into an open-source Postman. This doesn't mean we will not tackle this issue (this issue is still open and will remain open until a solution is pushed), but we are planning on a solution we think is more better suited for the documentation way of doing things, this will take some time though as we are focused on other things to tackle before going for this.

+1 for this feature

I think this feature is connected with #1598. If we have the mock ability, then this feature is very convenient and can be a part of the mock feature

Also, I think it can be very convenient if we can generate API doc automated. But for now, I need to save my API doc in another place and rewrite the response again.

I'd like to look into implementing this feature.

@AndrewBastin Have you been able to find a solution yet? I agree that examples are more of a documentation, though having both integrated seamlessly works nicely sometimes. The way Postman handles it is quick and easy to access and reproduce.

Please let me know if there has been any progress in this regard.

Thanks

+1 For this Feature

Recently Switched to HoppScotch from postman, this feature would be a important addition. Any Updates on this? can i help in any way by contributing to the repo? i might need some guidance if anyone is able to help

I came across HoppScotch to find it as a lovely open source project, and it really is. But the only thing holding me back from migrating my projects to HoppScotch is ability save responses/mock/examples.

It is very convenient to save API response, right with the actual API, with certain payloads etc to give idea to team about different scenarios.

+1 to this feature please

+1 For this Feature

See also #2018 with respect to being able to save responses as 'examples'.

+1 For this Feature

+1

+1 for this feature

+1 for this feature

+1

can we have this feature plz 💯

+1

+1!
Please add soon.

+1 For this Feature.
Please.

+1 For this Feature.

+1

+1 need to. mock response examples! thanks

+1