[feature] Save response data into API definition #2331
Description
Is your feature request related to a problem? Please describe.
Currently, Reqable does not provide a way to save response data into the API definition.
When debugging an API, even if a request returns a correct and stable response, there is no built-in functionality to persist this response as part of the API (such as example data or reference response).
As a result, response data can only be viewed temporarily and cannot be reused or associated with the API itself.
Describe the solution you'd like
I would like Reqable to support saving response data directly into the API definition.
For example, after receiving a response, users could choose to:
- Save the response body as an example response
- Store it as reference data for the API
- Use it as a basis for mock or testing purposes
This would allow real response data to become part of the API lifecycle instead of being discarded after debugging.
Describe alternatives you've considered
At the moment, the only alternative is to manually copy the response data and paste it into the API definition or external documentation.
This approach is inefficient and breaks the workflow, especially when dealing with large or frequently changing responses.
Additional context
This feature would help bridge the gap between API debugging and API management in Reqable.
It would be especially useful for teams or individuals who use Reqable not only to inspect requests, but also to maintain API definitions, examples, and test data based on real responses.