[GH-ISSUE #3428] [feature]: REST api schemas #1155

New issue

Open

opened 2026-03-16 18:52:37 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 18:52:37 +03:00

Owner

Originally created by @KasKatto on GitHub (Oct 6, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3428

Is there an existing issue for this?

I have searched the existing issues

Summary

When designing REST api endpoints it would be useful to be able to set a request schema when using body content types like json. You would be able to specify what the structure of the json should look like. OpenAPI's component schema is what i have in mind.

Why should this be worked on?

The lack of being this feature means having to use external tools for API design, which adds complexity. Currently the closest you can get to a schema is having to provide a sample body into each request. This fine for data that can be stored in env variables, but for larger structures it gets very messy and pollutes the environment.

Originally created by @KasKatto on GitHub (Oct 6, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3428 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary When designing REST api endpoints it would be useful to be able to set a request schema when using body content types like json. You would be able to specify what the structure of the json should look like. OpenAPI's component schema is what i have in mind. ### Why should this be worked on? The lack of being this feature means having to use external tools for API design, which adds complexity. Currently the closest you can get to a schema is having to provide a sample body into each request. This fine for data that can be stored in env variables, but for larger structures it gets very messy and pollutes the environment.