It may be possible to port usage of the current webhook to use API calls from this library instead.
It's unclear if the API has 1-to-1 exposure of the same data as the webhook but it does at least have UserDataSaved(?) and playback/player state DTOs so it's at least worth investigating.
Switching to API means we can remove a layer of indirection (webhook plugin) which may help with resolving some longstanding issues:
87 - possibly timestamp is more consistent since it isn't interpreted by webhook?
70 - using api means we may be able to get all artists from playback finish event, or are able to make additional calls to get this information
Additional benefits:
Reduces network complexity for end-user since MS doesn't need to be accessible to JF
FoxxMD
commented
5 days ago
JF now has a TS client library for interacting with the API.
It may be possible to port usage of the current webhook to use API calls from this library instead.
It's unclear if the API has 1-to-1 exposure of the same data as the webhook but it does at least have
UserDataSaved(?) and playback/player state DTOs so it's at least worth investigating.Switching to API means we can remove a layer of indirection (webhook plugin) which may help with resolving some longstanding issues:
87 - possibly timestamp is more consistent since it isn't interpreted by webhook?
70 - using api means we may be able to get all artists from playback finish event, or are able to make additional calls to get this information
Additional benefits: