Support WebSocket Endpoints

[matanpramp]

Websocket support, even the most basic (no tests, code generation, collections), would be very useful.

Basic support IMO would be:

• the ability to establish connections
• read incoming messages
• send outgoing messages
• maintaining support for existing Postman features such as headers, cookies, viewing and editing the messages

Considering the nature of many modern, interactive web applications, web sockets are becoming a basic requirement for many backend automation tasks.

[SamvelRaja]

Thanks for your feedback. I am marking this a feature request. I cannot promise an ETA now.
We will update this thread when we pick this feature.

[binarymist]

How's progress?

[omar-haris]

Any news ?

[ikushnir]

Looking forward to have this feature !

[loveexception]

i 'm love this feature .

[supermacro]

joining the notification train

[cosad3s]

Same.

[calvincs]

ditto

[byronvoorbach]

+1

[jreisam]

@@ nothing?

[xukaifu]

this feature is awesome

[kienbui1995]

This feature is needed.
I think that many users want to it attach the app.
https://stackoverflow.com/questions/42269075/websocket-connections-with-postman/43754722#43754722

[maddestructor]

This feature would be a game changer to our team!

[wave100]

It'd be awesome if this became a feature!

[Whyner]

+1

[fborie]

+1

[duart38]

+9999 I've been using this as i work on some other projects. link

[tqwewe]

+69

[MaxVynohradov]

+1

[cisolarix]

+10086

[fredrickreuben]

+1

[me89]

maybe we should ask here:
https://community.getpostman.com/c/feature-requests

[supermacro]

Also, see roadmap (which sadly doesn't have any mention of websockets).

https://trello.com/b/4N7PnHAz/postman-roadmap-for-developers

Would be nice if the postman team would communicate why websockets seem to be such a low priority.

[libdefi]

+1

[1990prashant]

+1

[3rdstage]

+1

[BrettThib]

Yes, please!

[nazmulmamunh]

1

[brdilshod]

+1

[skybird23333]

just click the subscribe button to get notifs

[GioPan04]

This issue should be locked until any words from postman team

[dmartinsid]

+1

[jgowdy]

👍🏻
+1

[arlemi]

Hey everyone! If you're interested WebSocket's support in Postman you might want to join our livestream on YouTube or Twitch at 7PM PST tomorrow, we'll have some news to share!

And if you're not able to attend live, don't worry, we'll share the news here too. 😉

[appurva21]

Hello everyone 👋 !

We are immensely excited to announce that Postman now supports the testing of WebSocket APIs! 🎉

In the latest version of Postman, you can now hit the New button in the left sidebar and open a WebSocket Request tab. Check out our Learning Center documentation to know more about how to use Postman for WebSocket APIs

Read more about this on the Postman Blog and share your feedback with us in our discussion forum.

Lastly, a big shoutout to our Postman community for providing all the great suggestions here and being patient with us 🙌 !

[shamasis]

Thanks everyone for patiently waiting for this. Completing the loop around our API Platform constructs was crucial alongside plugging in other protocols.

I would like to extend a line to @matanpramp for reporting this feature request in the most succinct way possible and to @gepopa - the team is excited to someday meet and share 🍻. Not to mention every upvotes we received to understand what we need to build.

Support for subprotocols (Socket.io, etc) + integrating with collections to test, document, share and use AsyncAPI Schema are all coming soon. This is still in beta and our goal is to iterate based on your feedback. Please file feature requests as new issues and we will keep collating them.

[altruios]

Thanks everyone for patiently waiting for this. Completing the loop around our API Platform constructs was crucial alongside plugging in other protocols.

I would like to extend a line to @matanpramp for reporting this feature request in the most succinct way possible and to @gepopa - the team is excited to someday meet and share 🍻. Not to mention every upvotes we received to understand what we need to build.

Support for subprotocols (Socket.io, etc) + integrating with collections to test, document, share and use AsyncAPI Schema are all coming soon. This is still in beta and our goal is to iterate based on your feedback. Please file feature requests as new issues and we will keep collating them.

okay - so socket.io is not yet supported? (wish I found this post yesterday, lol), any timeline on when socket.io support might be?

[shamasis]

Thanks everyone for patiently waiting for this. Completing the loop around our API Platform constructs was crucial alongside plugging in other protocols.
I would like to extend a line to @matanpramp for reporting this feature request in the most succinct way possible and to @gepopa - the team is excited to someday meet and share 🍻. Not to mention every upvotes we received to understand what we need to build.
Support for subprotocols (Socket.io, etc) + integrating with collections to test, document, share and use AsyncAPI Schema are all coming soon. This is still in beta and our goal is to iterate based on your feedback. Please file feature requests as new issues and we will keep collating them.

okay - so socket.io is not yet supported? (wish I found this post yesterday, lol), any timeline on when socket.io support might be?

Socket.io is already supported. @codenirvana is writing a doc around the specifics. However we want to also build a more dedicated UI support for Socket.io so that you do not need to know the underlying workings of Socket.io while using Postman. That extended support is coming up next. We need to iron out some design concepts before we can confidently convey a date.

[prabhakarj13]

@shamasis is there any support of subprotocols: graphql-ws for websocket

[codenirvana]

@prabhakarj13 not yet.

Please follow #9997 for updates on subprotocols support.

[shirshak55]

looks like its not implemented properly. Like I need to go to new and click on websocket? Why not just new tab and check if url has ws:// or wss://? Like how do new user literally discover how to use websockets?

And second we cannot save? Like if there is multiple message if we disconnect and reconnect we lose all the message? I hope this will be fixed once beta is over. But closing this issue without implementing fully might be premature?

[arlemi]

@shirshak55 You can access previous requests/message history from the History tab (left sidebar). The feature is still in beta and we'll be building on top of the feedback we receive here.

[shamasis]

@shirshak55 ... thank you for the feedback. @arlemi answered one of your questions.

In the grand scheme of API lifecycle, there is a lot more to do for WebSockets and the current implementation enables the core constructs as described in this issue. #4009 (comment)

We are tracking all subsequent bugs and feature requests separately to ensure everything is not stuffed in one long running issue for many years! Please use this GH label to see what we have distilled so far https://github.com/postmanlabs/postman-app-support/labels/websocket

I would really love to read more on how you are using Websocket within Postman and the things that we can do when we save a websocket request within a collection.

[shirshak55]

Actually, history is not that good tbh. Because after testing one or two endpoint and updating messages there are hundreds of history and I don't know what are the changes. I think it will be improved in future. Can't we just save the request just like another http get/post etc?

I understand ws is a different beast but I wished ws would get more focus. The web is no longer just http1.1.

And history doesn't work afaik.

[shamasis]

Actually, history is not that good tbh. Because after testing one or two endpoint and updating messages there are hundreds of history and I don't know what are the changes. I think it will be improved in future. Can't we just save the request just like another http get/post etc?

I understand ws is a different beast but I wished ws would get more focus. The web is no longer just http1.1.

Keep your eyes on our Twitter and release notes. More on ws will keep coming in more often. Socket.io support and collection integration (in some limited scope though.)

[meenakshi-dhanani]

You might be interested in a live stream happening today about how the Postman team built support for web sockets, join us with all your questions - YouTube or Twitch 8am PT

[shamasis]

Actually, history is not that good tbh. Because after testing one or two endpoint and updating messages there are hundreds of history and I don't know what are the changes. I think it will be improved in future. Can't we just save the request just like another http get/post etc?

I understand ws is a different beast but I wished ws would get more focus. The web is no longer just http1.1.

Keep your eyes on our Twitter and release notes. More on ws will keep coming in more often. Socket.io support and collection integration (in some limited scope though.)

Socket.IO support is now available on latest Postman - https://blog.postman.com/postman-now-supports-socket-io/

[vansham-gortnm]

I am wondering how to emit an event to the socket.io based socket server. There appears to be no concise explanation for that and everytime I try to emit anything, the connection closes.

[codenirvana]

@vansham-gortnm can you create a new bug report or reaching out to the wider Postman Community for help?

Locking this closed thread conversation to avoid unnoticed bug reports and feature requests.

---

Everyone, feel free to raise a feature request and bug report related to WebSocket request here: https://github.com/postmanlabs/postman-app-support/issues/new/choose