Update Jellyfin API query parameter naming

While reviewing Infuse’s network interaction with my Jellyfin server I noticed Infuse sends query parameters as CamelCase while according to Jellyfin’s API spec these should be lowerCamelCase.

In LowerCameCase the first word starts with a lowercase letter, and each subsequent word starts with an uppercase letter.

Examle API call, in

/Users/XAOVn7iqiBujnIQY8sd0/Items/rVFG3EzPthk2wowNkqUl?Fields=DateCreated

Fields should be fields:

/Users/XAOVn7iqiBujnIQY8sd0/Items/rVFG3EzPthk2wowNkqUl?fields=DateCreated

Jellyfin’s API spec Jellyfin - ReDoc shows each query parameter name starts with a lowercase letter, and each subsequent word starts with an uppercase letter:

Also, the HTTP spec states query parameter names are case sensitive..

I’ve seen this for the following parameters provided by Infuse:

ParentId should be parentId
SearchTerm → searchTerm
Fields → fields
SortBy → sortBy
SortOrder → SortOrder
StartIndex → startIndex
Limit → limit
SeasonId → seasonId

but there might be more..

It might be good to adjust these so names provided exactly match the Jellyfin API spec.

1 Like

Thanks for the report!

Today’s 8.1.7 update some API cleanup for Jellyfin which should address these cases and help avoid potential issues in the future. :slight_smile:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.