While reviewing Infuse’s network interaction with my Jellyfin server I noticed Infuse uses paths. Paths embedding userid appear to be deprecated, the official approach is to provide userid as a query parameter.
Example API call:
/Users/XAOVn7iqiBujnIQY8sd0/Items/rVFG3EzPthk2wowNkqUl?Fields=DateCreated
should probably be:
/Items/rVFG3EzPthk2wowNkqUl?UserId=XAOVn7iqiBujnIQY8sd0&Fields=DateCreated
Jellyfin’s API spec Jellyfin - ReDoc shows userId is a query parameter these days:
It might be good to future proof by switching from path to query parameter-based provided UserId in Jellyfin API calls.
(Also see Update Jellyfin API query parameter naming for another minor Jellyfin API thing)
