You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 11, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 11, 2025. It is now read-only.
As it stands, the Skype "messaging hosts" (i.e. the bulk of APIs for sending/receiving messages and listening for events) appear to have been replaced with a Teams-domain stand-in providing just enough functionality to keep Skype for Web running (e.g. it doesn't include the event subscription APIs). It's unclear what will happen after migration; my guess is this will be retired entirely and Teams will use its own APIs (e.g. real-time notifications seem to be done with a websocket rather than HTTP long-poll) going forward.
On top of that, a new authentication flow will likely be needed, as the Skype SOAP endpoint will almost certainly will stop working, and the Microsoft account flow is still wrapped by Skype APIs to generate its own tokens. Until Skype properly shuts down, it's not immediately clear how much of the existing web APIs across Skype and Teams are transitional.
SkPy is an old library (it was originally written for Python 2.6 and likely still more-or-less works there, as far as the APIs allow!), and I stopped using Skype for personal communication about 8 years ago. I've been trying to keep the lights on in the meantime, but this seems like the obvious point to wind things down -- I have no intention of using Teams going forward.
The best case scenario is all of the endpoints continue working (i.e. Microsoft add the old event APIs to their Teams messaging host) and the flows just need updating with new URLs, but I suspect most things will need rewriting after Skype's shutdown in May. Changes needed to keep things working through the Teams transition are in #294. The code will stay up for anyone willing to figure out the necessary changes after that.
Activity
Terrance commentedon Apr 6, 2025
As it stands, the Skype "messaging hosts" (i.e. the bulk of APIs for sending/receiving messages and listening for events) appear to have been replaced with a Teams-domain stand-in providing just enough functionality to keep Skype for Web running (e.g. it doesn't include the event subscription APIs). It's unclear what will happen after migration; my guess is this will be retired entirely and Teams will use its own APIs (e.g. real-time notifications seem to be done with a websocket rather than HTTP long-poll) going forward.
On top of that, a new authentication flow will likely be needed, as the Skype SOAP endpoint will almost certainly will stop working, and the Microsoft account flow is still wrapped by Skype APIs to generate its own tokens. Until Skype properly shuts down, it's not immediately clear how much of the existing web APIs across Skype and Teams are transitional.
SkPy is an old library (it was originally written for Python 2.6 and likely still more-or-less works there, as far as the APIs allow!), and I stopped using Skype for personal communication about 8 years ago. I've been trying to keep the lights on in the meantime, but this seems like the obvious point to wind things down -- I have no intention of using Teams going forward.
The best case scenario is all of the endpoints continue working (i.e. Microsoft add the old event APIs to their Teams messaging host) and the flows just need updating with new URLs, but I suspect most things will need rewriting after Skype's shutdown in May. Changes needed to keep things working through the Teams transition are in #294. The code will stay up for anyone willing to figure out the necessary changes after that.