[GH-ISSUE #5011] [feature]: Websocket requests as a REST request #1908

New issue

Open

opened 2026-03-16 22:20:19 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 22:20:19 +03:00

Owner

Originally created by @nrbnlulu on GitHub (Apr 22, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5011

Is there an existing issue for this?

I have searched the existing issues

Summary

WS requests are saved / shared in workspaces.
it should be possible to set headers for the WS request just like any other REST calls.

a WS request is basically an HTTP request that was migrated to a long running protocol.

Why should this be worked on?

useful for saving ws requests between workspace members + saving them for later + using variables etc.
lots of API's these days use sockets that require some kind of authorization token. while from a research from other issues and from
looking on some chat web apps it seems like they put the token in the url (prob due to a limitation in the default web socket implementation
by JS specs IDRC), some API's prefer to use an header.

even if thats wrong to do that (for some reason IDK) its still a fact that lots of API's do that so would be legit if hoppscotch support it.

Originally created by @nrbnlulu on GitHub (Apr 22, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5011 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary 1. WS requests are saved / shared in workspaces. 2. it should be possible to set headers for the WS request just like any other REST calls. a WS request is basically an HTTP request that was migrated to a long running protocol. ### Why should this be worked on? 1. useful for saving ws requests between workspace members + saving them for later + using variables etc. 2. lots of API's these days use sockets that require some kind of authorization token. while from a research from other issues and from looking on some chat web apps it seems like they put the token in the url (prob due to a limitation in the default web socket implementation by JS specs IDRC), some API's prefer to use an header. even if thats wrong to do that (for some reason IDK) its still a fact that lots of API's do that so would be legit if hoppscotch support it.

kerem added the

feature

label

2026-03-16 22:20:19 +03:00

kerem commented

2026-03-16 22:20:30 +03:00

Author

Owner

@030201xz commented on GitHub (Sep 20, 2025):

This feature is very useful, I like hoppscotch, but because I can't save an instance of a websocket request, I have to use APIFOX again and open both API test tools at the same time...

@030201xz commented on GitHub (Sep 20, 2025): This feature is very useful, I like hoppscotch, but because I can't save an instance of a websocket request, I have to use APIFOX again and open both API test tools at the same time...

kerem commented

2026-03-16 22:20:35 +03:00

Author

Owner

@d1hr2uv commented on GitHub (Jan 14, 2026):

Voiden does support the headers block with websocket !

Use it here : https://voiden.md/

@d1hr2uv commented on GitHub (Jan 14, 2026): Voiden does support the headers block with websocket ! Use it here : https://voiden.md/