WebSockets endpoints? #255

Closed
opened 2026-02-04 19:01:39 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @rcdailey on GitHub (Mar 11, 2019).

Using this guide: https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-WebSocket-notifications

It is stated that the following endpoints must be considered:

  • /notifications/hub
  • /notifications/hub/negotiate

However, while I do not remember where I got it, I also am mapping /api/websocket. Is this a valid endpoint in the latest version? Or is this incorrect / outdated?

Originally created by @rcdailey on GitHub (Mar 11, 2019). Using this guide: https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-WebSocket-notifications It is stated that the following endpoints must be considered: * `/notifications/hub` * `/notifications/hub/negotiate` However, while I do not remember where I got it, I also am mapping `/api/websocket`. Is this a valid endpoint in the latest version? Or is this incorrect / outdated?
Author
Owner

@dani-garcia commented on GitHub (Mar 12, 2019):

I don't think we ever had that endpoint, no. Just the two that you list first. They are also the same that the official server uses, so I don't know where that one could have come from. You should be able to delete it without problems.

@dani-garcia commented on GitHub (Mar 12, 2019): I don't think we ever had that endpoint, no. Just the two that you list first. They are also the same that the official server uses, so I don't know where that one could have come from. You should be able to delete it without problems.
Author
Owner

@rcdailey commented on GitHub (Mar 12, 2019):

Thank you!

@rcdailey commented on GitHub (Mar 12, 2019): Thank you!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#255